CVE-2026-123037

Ansible-core: user module generate_ssh_key follows a symlinked ~/.ssh enabling local privilege escalation (incomplete fix of cve-2024-9902)

  • Medium 6.7

Description

A flaw was found in the ansible-core user module. When generate_ssh_key is enabled, User.ssh_key_gen() guards the key files against symlinks but checks the ~/.ssh directory only with os.path.exists(). An unprivileged user on a managed node who replaces their ~/.ssh with a symlink to an existing root-writable directory causes the privileged module to write the generated key pair through the symlink and then chown both files to that user. Because such files can be dropped into directories processed by schedulers (e.g. /etc/cron.daily) or dynamic MOTD (/etc/update-motd.d), the user can escalate to root on the managed node. This is an incomplete fix of CVE-2024-9902.

Key facts

Published
6 Nov 2026
Last changed
6 Nov 2026
Assigned by
redhat
EPSS
0.111% likely to be exploited in the next 30 days, higher than 1.377% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.7CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

What to do

  • Do not use generate_ssh_key: yes against accounts whose home directory is controlled by an untrusted user; pre-create ~/.ssh as a real directory owned appropriately before running the module, or generate the key as the target account itself (dropping to its uid/gid) rather than as root.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatMigration Toolkit for Applications 8
  • Default status: affected
Red HatMigration Toolkit for Virtualization
  • Default status: affected
Red HatMigration Toolkit for Virtualization
  • Default status: affected
Red HatOpenShift Service Mesh 3
  • Default status: affected
Red HatRed Hat Advanced Cluster Management for Kubernetes 2
  • Default status: affected
Red HatRed Hat Advanced Cluster Management for Kubernetes 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: unaffected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform Ansible Core 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform Ansible Core 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform Ansible Core 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform Ansible Core 2
  • Default status: affected
Red HatRed Hat Discovery 2
  • Default status: affected
Red HatRed Hat Enterprise Linux 10
  • Default status: affected
Red HatRed Hat Enterprise Linux 8
  • Default status: affected
Red HatRed Hat Enterprise Linux 9
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 5
  • Default status: affected
Red HatRed Hat Satellite 6
  • Default status: affected
Red HatSelf-service automation portal 2
  • Default status: affected
Red HatService Telemetry Framework 1.5
  • Default status: affected
Red HatService Telemetry Framework 1.5
  • Default status: affected

Timeline

  1. 5 Nov 2026 Reported to Red Hat.
  2. 5 Nov 2026 Made public.
  3. 6 Nov 2026 Published

Weakness

References