CVE-2026-111456
Description
A missing authorization check has been found in ConsumerResource.setupOwner() function of consumer registration module in the Candlepin package. The registration method checks permission to create a consumer only when the caller is a user. A consumer that authenticates with its identity certificate does not go through that check. A low-privileged network attacker or user who has a valid consumer certificate for one organization can register a new consumer in a different organization by supplying that organization's key. The response includes an identity certificate for the new consumer. With that certificate, the attacker can view the target organization's subscription pools. When the organization is not using simple content access, the attacker can attach that organization's entitlements to the new consumer.
Statement
Red Hat Product Security has rated this vulnerability with an Important security impact. This vulnerability affects candlepin's consumer registration handling.
The attacker needs a valid consumer identity certificate and the key of another organization. SSL client authentication is enabled by default. The deployment must contain more than one organization.
The vulnerable check was introduced in candlepin 0.4.7, when owner authorization during registration was limited to user principals so that activation-key registration could succeed. Candlepin versions from 0.4.7 onward contain the check.
Red Hat Satellite 6.16 and 6.17 ships Candlepin 4.4.25. Satellite 6.18 ships 4.6.6, Satellite 6.19 ships 4.7.5. All Satellite versions are affected. Registered systems reach this API with their consumer certificates in the default Satellite configuration.
Mitigation
There is no configuration switch that stops a consumer certificate from calling registration while leaving normal consumer check-ins working. Restricting which clients can reach the Candlepin port limits who can attempt the call, and it does not stop a client that already has a valid consumer certificate and is allowed to use the API. Customers are advised to apply the relevant security updates when they become available.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.1 | N/A | 7.1 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | Low | N/A | Low |
| Integrity Impact | High | N/A | High |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism
Access control checks for specific user data or functionality can be bypassed.
Access Control
Technical Impact: Gain Privileges or Assume Identity
Horizontal escalation of privilege is possible (one user can view/modify information of another user).
Access Control
Technical Impact: Gain Privileges or Assume Identity
Vertical escalation of privilege is possible if the user-controlled key is actually a flag that indicates administrator status, allowing the attacker to gain administrative access.
Acknowledgements
Red Hat would like to thank Farid Narimanov for reporting this issue.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
