Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-12515 medium CVSS 4.3

Vulnerability in katello (CVE-2026-12515)

Summary

Vulnerability in katello (CVE-2026-12515). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.21.0.rc1 or later.

Original description

The description as published by the source.

A flaw was found in Katello's of Red Hat Satellite. A content upload functionality where insufficient authorization checks in the ContentUploadsController allowed users with the edit_products permission to query content information for repositories outside the products they were authorized to manage. An authenticated attacker could exploit this issue to determine whether specific content exists within repositories that should otherwise be inaccessible. This issue does not allow unauthorized modification, import, or publication of content.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-12515 has been found in katello.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade katello to 4.21.0.rc1 or later.
If unsure, ask your IT team or search "katello CVE-2026-12515" on the vendor's site.

CVE-2026-12515 (katello) — CWE-862 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.21.0.rc1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-862) exists in katello.

📍 Affected scope

Check the vendor advisory for the affected versions of katello.

🔥 Severity

Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 4.21.0.rc1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'katello' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'katello' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で katello を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade katello to 4.21.0.rc1

    ステージング環境で 4.21.0.rc1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

rubygems katello
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.21.0.rc1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details