Red Hat Satellite: Authorization Bypass Through User-Controlled Key (CVE-2026-86323)
Published Last modified Sources: CVE.org, EUVD
What is affected, what to do
A flaw was found in Foreman’s Api::V2::MailNotificationsController, where authorization checks on user-specific mail-notification resources are insufficient. The GET /api/v2/users/:id/mail_notifications endpoint resolves the target account using User.find(params[:id]) without verifying that the authenticated user is authorized to access that user’s notification configuration.
Update Red Hat Satellite 6.16 for RHEL 8 to version 0:3.12.0.26-1.el8sat, Red Hat Satellite 6.16 for RHEL 9 to version 0:3.12.0.26-1.el9sat, Red Hat Satellite 6.17 for RHEL 9 to version 0:3.14.0.26-1.el9sat.
- Affected
- Red Hat Satellite 6.16 for RHEL 8
lt *..0:3.12.0.26-1.el8sat - Red Hat Satellite 6.16 for RHEL 9
lt *..0:3.12.0.26-1.el9sat - Red Hat Satellite 6.17 for RHEL 9
lt *..0:3.14.0.26-1.el9sat - Red Hat Satellite 6.18 for RHEL 9
lt *..0:3.16.0.29-1.el9sat
- Red Hat Satellite 6.16 for RHEL 8
- Fixed in
- Red Hat Satellite 6.16 for RHEL 8
0:3.12.0.26-1.el8sat - Red Hat Satellite 6.16 for RHEL 9
0:3.12.0.26-1.el9sat - Red Hat Satellite 6.17 for RHEL 9
0:3.14.0.26-1.el9sat - Red Hat Satellite 6.18 for RHEL 9
0:3.16.0.29-1.el9sat
- Red Hat Satellite 6.16 for RHEL 8
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
4.3
XIEM Effective CVSS
Highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
4.3
CVSS v3
Severity Medium on the scale from 0 to 10.
Source: CVE.org, EUVD
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- Medium
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 51.50 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 4.3 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 4.3
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-639
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
A flaw was found in Foreman’s Api::V2::MailNotificationsController, where authorization checks on user-specific mail-notification resources are insufficient. The GET /api/v2/users/:id/mail_notifications endpoint resolves the target account using User.find(params[:id]) without verifying that the authenticated user is authorized to access that user’s notification configuration. Additionally, the POST and PUT /api/v2/users/:user_id/mail_notifications paths call deny_access when the requester is unauthorized but fail to halt execution, allowing the request to continue and persist the unauthorized change despite a 403 response or subsequent DoubleRenderError. This can allow a user to disclose another user’s mail-notification configuration, including mail_query values, and, where write permissions apply, modify or create notification settings for another user.
Source: NVD (NIST), ENISA EUVD, cvelistv5, CVE.org (MITRE)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Red Hat | Red Hat Satellite 6.16 for RHEL 8 |
|
|
| Red Hat | Red Hat Satellite 6.16 for RHEL 9 |
|
|
| Red Hat | Red Hat Satellite 6.17 for RHEL 9 |
|
|
| Red Hat | Red Hat Satellite 6.18 for RHEL 9 |
|
|
Vendors and products
Weakness classes (CWE)
CWE-639Authorization Bypass Through User-Controlled Key
Base
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Entry at MITRE CWE-639
References & sources
- access.redhat.comsecurity/cve/CVE-2026-86323euvd, Vulnerability database, x_refsource_REDHAT
- bugzilla.redhat.comRHBZ#2529290euvd, Issue tracking, x_refsource_REDHAT
- NVD (NIST)vuln/detail/CVE-2026-86323euvd
- access.redhat.comRHSA-2026:99949euvd, Vendor advisory, x_refsource_REDHAT
- access.redhat.comRHSA-2026:99950euvd, Vendor advisory, x_refsource_REDHAT
- access.redhat.comRHSA-2026:99952euvd, Vendor advisory, x_refsource_REDHAT
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedRed Hat
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/86xxx/CVE-2026-86323.json">CVE-2026-86323</a>Reference added —https://access.redhat.com/errata/RHSA-2026:99949Reference added —https://access.redhat.com/errata/RHSA-2026:99950Reference added —https://access.redhat.com/errata/RHSA-2026:99952Source identifier: secalert@redhat.com
ReceivedRed Hat
CVSS V3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Weakness type: CWE-639
Description added or changed
Show 6 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —A flaw was found in Foreman’s Api::V2::MailNotificationsController, where authorization checks on user-specific mail-notification resources are insufficient. The GET /api/v2/users/:id/mail_notifications endpoint resolves the target account using User.find(params[:id]) without verifying that the authenticated user is authorized to access that user’s notification configuration. Additionally, the POST and PUT /api/v2/users/:user_id/mail_notifications paths call deny_access when the requester is unauthorized but fail to halt execution, allowing the request to continue and persist the unauthorized change despite a 403 response or subsequent DoubleRenderError. This can allow a user to disclose another user’s mail-notification configuration, including mail_query values, and, where write permissions apply, modify or create notification settings for another user.CVSS added —AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NWeakness type (CWE) added —CWE-639Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/86xxx/CVE-2026-86323.json">CVE-2026-86323</a>Reference added —https://access.redhat.com/security/cve/CVE-2026-86323Reference added —https://bugzilla.redhat.com/show_bug.cgi?id=2529290Source identifier: secalert@redhat.com
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-86323"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-86323.svg?lang=en" alt="CVE-2026-86323 – NEOSEC Intel" height="20"></a>