CVE-2026-86324
Awaiting Analysis Awaiting Analysis - Queue

Foreman Authorization Bypass via SSH Key Injection

Vulnerability report for CVE-2026-86324, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-12

Last updated on: 2026-11-12

Assigner: redhat-SADP

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-12
Last Modified
2026-11-12
Generated
2026-11-12
AI Q&A
2026-11-12
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Red Hat Red Hat Satellite 6 *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 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.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an authorization bypass in Foreman's Api::V2::SshKeysController. It allows an attacker with the create_ssh_keys permission to inject their own public SSH key into another user's account by exploiting a missing parent-user authorization check. The injected key is then used during host provisioning, potentially granting the attacker SSH access to the victim's managed systems.

Detection Guidance

To detect this vulnerability, monitor Foreman API logs for suspicious POST requests to /api/v2/users/:user_id/ssh_keys where the user_id does not match the authenticated user. Check for unauthorized SSH key additions in user accounts by reviewing Foreman's user management interface or database queries for unexpected key entries.

Impact Analysis

If you are a user with the create_ssh_keys permission in Foreman, an attacker could exploit this to add their SSH key to your account. This would allow them to authenticate to and gain control over hosts you manage via SSH. The attack does not require user interaction and has low integrity impact.

Compliance Impact

This vulnerability could lead to unauthorized access to systems, potentially violating compliance requirements for data protection and access control in standards like GDPR and HIPAA. Unauthorized SSH access may result in data breaches or unauthorized modifications, impacting confidentiality and integrity.

Mitigation Strategies

Apply the latest Foreman security patches or updates immediately. Temporarily restrict the create_ssh_keys permission to trusted users only. Review all SSH keys in user accounts for unauthorized additions and remove any suspicious keys. Monitor network traffic for unusual SSH access attempts from managed hosts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-86324. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...