cve.bz

CVE-2026-86324

Foreman: authorization flaw in the foreman::controller::useraware handling used by api::v2::sshkeyscontroller

4.3 medium

Medium (4.3) in red hat red hat satellite 6.

On this page
A flaw was found in Foreman’s Api::V2::SshKeysController, where the target user is resolved through Foreman::Controller::UserAware#find_user using User.find(params[:user_id]) without enforcing the required parent-user authorization check. An attacker with the create_ssh_keys permission can exploit this authorization bypass by submitting POST /api/v2/users/:user_id/ssh_keys with another user’s ID and injecting their own public SSH key into the targeted account. The injected key is subsequently propagated to hosts provisioned by that user, potentially allowing the attacker to authenticate to and gain SSH access to the victim’s managed hosts.

Severity

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
redhat (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-86324 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-86324?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-86324?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-86324 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-86324

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-86324](https://cve.bz/cve/badge/CVE-2026-86324.svg)](https://cve.bz/cve/CVE-2026-86324)

HTML:

<a href="https://cve.bz/cve/CVE-2026-86324"><img src="https://cve.bz/cve/badge/CVE-2026-86324.svg" alt="CVE-2026-86324"></a>

Affected

  • red hat:red hat satellite 6

References

Check your stackJSON