GHSA-c43c-rf7g-5xpg CVE-2026-12515
katello: missing repository authorization in content_uploads exposes cross-product content existence
- Severity
- 4.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.22%
- Chance of exploitation in the next 30 days. Higher than 12.91% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-862 Missing Authorization
- Fix
4.21.0.rc1- Upgrade katello to this version or later
Description
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.
Affected versions
RubyGems
| Package | Vulnerable | Fixed in |
|---|---|---|
| katello | < 4.21.0.rc1 |
4.21.0.rc1 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
katello RubyGems → 4.21.0.rc1
- bundler
bundle update katello # Gemfile: gem "katello", ">= 4.21.0.rc1"
Severity breakdown
CVSS 3.1 4.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-862: Missing Authorization
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
How to prevent it
- Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Architecture and Design: Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
- Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
- System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.
References
Advisories
Packages
Other links
- github.com/Katello/katello/pull/11712
- access.redhat.com/errata/RHSA-2026:50221
- access.redhat.com/errata/RHSA-2026:50222
- access.redhat.com/errata/RHSA-2026:50223
- access.redhat.com/errata/RHSA-2026:50263
- access.redhat.com/security/cve/CVE-2026-12515
- bugzilla.redhat.com/show_bug.cgi
- github.com/rubysec/ruby-advisory-db/blob/master/gems/katello/CVE-2026-12515.yml
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-fwj4-6wgp-mpxm Katello: Denial of Service and potential information disclosure via SQL injection | Medium | Also affects katello |
| GHSA-m4wh-848j-9w2r Katello cleartext password storage issue | Low | Also affects katello |
| GHSA-5xv2-q475-rwrh Katello uses hard coded credential | Critical | Also affects katello |
| GHSA-527r-mfmj-prqf Katello SQL Injection vulnerabilities | High | Also affects katello |
| GHSA-mhhc-r88h-2qrm katello Cross-site Scripting vulnerability | Medium | Also affects katello |
| GHSA-cpv6-pfq6-j2v7 katello Improper Privilege Management vulnerability | Medium | Also affects katello |
| GHSA-jx5v-788g-qw58 katello SQL Injection vulnerability | Medium | Also affects katello |
| GHSA-vp5q-ff62-jwqv russh: Agent server never calls `Agent::confirm`, so keys added with the confirm constraint (`ssh-add -c`) sign without confirmation | High | Same weakness, CWE-862 |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor