CVE
Red Hat Satellite unauthorized access to mail-notification settings in API
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.36% · 29th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 22/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Red Hat Satellite 6 (the foreman package) has an authorization flaw in its mail-notification endpoints. A remote attacker with a low-privileged login and no user interaction can view another user's mail-notification settings, including mail_query values, and, where write permissions apply, change or create those settings.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach10/20Shipped in major Linux distributions
- Severity4.3/10CVSS 4.3
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 41 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-86323 (Foreman: authorization flaw in the mail-notification endpoints implemented by api::v2::mailnotificationscontroller), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-86323 (entry last updated 2026-11-13):
Affected:
- Red Hat Red Hat Satellite 6.16 for RHEL 8: version range not reported
- Red Hat Red Hat Satellite 6.16 for RHEL 9: version range not reported
- Red Hat Red Hat Satellite 6.17 for RHEL 9: version range not reported
- Red Hat Red Hat Satellite 6.18 for RHEL 9: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-86323 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-86323 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://access.redhat.com/errata/RHSA-2026:99949
- https://access.redhat.com/errata/RHSA-2026:99950
- https://access.redhat.com/errata/RHSA-2026:99952
- https://bugzilla.redhat.com/show_bug.cgi?id=2529290
- https://access.redhat.com/security/cve/CVE-2026-86323
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-86323
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-86323"}.Timeline
- CVE published
- First seen by cve.now1 day
- Record last updated
Affected versions
- foreman
Version range not reported
- foreman
Version range not reported
- foreman
Version range not reported
- foreman
Version range not reported
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Write-ups · 1
Establishes: Technical detail and context.
- Report
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.