CVE
Red Hat Satellite authorization bypass in personal access token API
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Attacker must hold the create_personal_access_tokens permission Target user account must be accessible by ID within the attacker's taxonomy scope
- 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.40% · 34th 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? →
- 32/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- 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's foreman package has an authorization flaw that lets a remote attacker with low-privilege login access and the create_personal_access_tokens permission create a personal access token for another user, including administrator accounts. The attacker can then use that token to sign in as the victim and take over the account.
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::PersonalAccessTokensController, where Foreman::Controller::UserAware#find_user resolves the target account using User.find(params[:user_id]) without applying the required parent-user authorization check. An attacker with the create_personal_access_tokens permission can therefore invoke POST /api/v2/users/:user_id/personal_access_tokens with another user’s ID and create a Personal Access Token on their behalf. The resulting plaintext token is returned in the API response, while PersonalAccessToken#check_permissions_after_save only validates create_personal_access_tokens on the token and does not enforce edit_users authorization on the target user. The attacker can then use the forged token to authenticate as the victim, potentially resulting in complete account takeover, including administrator accounts.
Who should check
Teams running Red Hat Satellite 6.16 (RHEL 8 and 9), 6.17 or 6.18 (RHEL 9) servers that expose the Foreman API
Read the source excerpt
“An update is now available for Red Hat Satellite 6.16 for RHEL 8 and RHEL 9.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Shipped in major Linux distributions
- Severity8.8/10CVSS 8.8
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
- Would score about 39 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Attacker must hold the create_personal_access_tokens permission Target user account must be accessible by ID within the attacker's taxonomy scopeWorkaround: The checked facts do not name a workaround. Limiting who holds the create_personal_access_tokens permission and reviewing taxonomy scopes would remove the conditions the attack needs, but this is an inference from the stated conditions, not a vendor-stated workaround.
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-86322 (Foreman: authorization flaw in the foreman::controller::useraware#find_user handling used by api::v2::personalaccesstokenscontroller), 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-86322 (entry last updated 2026-11-12):
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.
Conditions (all must be true for the bug to be hit):
- Attacker must hold the create_personal_access_tokens permission (source: https://bugzilla.redhat.com/show_bug.cgi?id=2529289)
- Target user account must be accessible by ID within the attacker's taxonomy scope (source: https://bugzilla.redhat.com/show_bug.cgi?id=2529289)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-86322 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-86322 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=2529289
- https://access.redhat.com/security/cve/CVE-2026-86322
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-86322
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-86322"}.Timeline
- CVE published
- First seen by cve.now
- 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.
Questions about CVE-2026-86322
Is CVE-2026-86322 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A user with the create_personal_access_tokens permission can forge a Personal Access Token for another user and authenticate as that user. This can lead to full account takeover, including administrator accounts that are visible within the attacker's taxonomy scope.Source: bugzilla.redhat.com
Am I affected, and how do I check?
The listed products are Red Hat Satellite 6.16 for RHEL 8, Red Hat Satellite 6.16 for RHEL 9, Red Hat Satellite 6.17 for RHEL 9, and Red Hat Satellite 6.18 for RHEL 9. Exposure depends on holding the create_personal_access_tokens permission and on the target account being accessible by ID within the user's taxonomy scope, so check your Satellite version and the permissions assigned to your accounts.Source: bugzilla.redhat.com
How do I fix CVE-2026-86322?
The checked facts do not name a fixed version or vendor patch IDs, so no upgrade target can be stated here. Check the vendor advisory for a fix before relying on any version.Source: bugzilla.redhat.com
What if there's no patch?
The checked facts do not name a workaround. Limiting who holds the create_personal_access_tokens permission and reviewing taxonomy scopes would remove the conditions the attack needs, but this is an inference from the stated conditions, not a vendor-stated workaround.Source: bugzilla.redhat.com