Quick answers
- Is CVE-2026-12515 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-12515 being exploited in the wild.
- How severe is CVE-2026-12515?
- Medium severity, with a CVSS score of 4.3, published 17 June 2026.
- Which products and versions are affected?
- katello (RubyGems) ECOSYSTEM:introduced=0,fixed=4.21.0.rc1.
- Is there a fix for CVE-2026-12515?
- Yes. katello (RubyGems): upgrade to 4.21.0.rc1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-12515 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-12515?
- Check whether you run katello (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- katello (RubyGems): upgrade to 4.21.0.rc1 or later
bundle update katello
Technical details
A missing object-level authorization check was identified in Katello's ContentUploadsController. The vulnerability exists because the controller does not enforce product-scoped authorization on the repository_id parameter. An authenticated attacker with 'edit_products' permissions for a specific subset of products can call the /katello/api/v2/repositories/:id/content_uploads endpoint against repositories outside their authorized scope. This allows the attacker to perform an information disclosure attack to determine if specific content exists in restricted repositories, though it does not permit modification, import, or publication of that content.
Affected products
- Red Hat Red Hat Satellite 6 6.x
- Katello Katello
Identifiers
- CVE-2026-12515
- GHSA-c43c-rf7g-5xpg
Timeline
- 2026-04-16: patched: Fix submitted via GitHub pull request 11712
- 2026-06-17: disclosed: Initial vulnerability report and CVE assignment