katello: missing repository authorization in content_uploads exposes cross-product content existence

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-12515: 0.22% estimated exploitation activity in the next 30 days; percentile 12.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 editproducts 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.

Published by the source

17 Jun 2026, 18:35 UTC

Last modified by the source

5 Aug 2026, 00:30 UTC

Source last checked

26 Oct 2026, 15:52 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c43c-rf7g-5xpg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-12515

Advisory: katello: missing repository authorization in content_uploads exposes cross-product content existence
IDs: CVE-2026-12515, GHSA-c43c-rf7g-5xpg
Record: https://patchnext.com/advisories/cve-2026-12515 (revision 1, source checked 26 Oct 2026, 15:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: katello 4.21.0.rc1. A vendor fix does not mean a deployment is fixed.

## Affected components
- RubyGems katello: affected < 4.21.0.rc1; fixed in 4.21.0.rc1

## Suggested inspection (read-only)
- RubyGems katello: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on katello.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c43c-rf7g-5xpg (GitHub-reviewed advisory GHSA-c43c-rf7g-5xpg lists affected ranges: RubyGems katello >=0 <4.21.0.rc1)

Commands are suggestions: review each one before running it.