Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
3.9

CVE-2026-126644: Red Hat Enterprise Linux: Ansible can write outside intended directory

CVE-2026-126644 · published 10 days ago
Summary

The Ansible authorized_key module can follow a symbolic link in a user’s .ssh folder, causing files to be created or overwritten in any directory the link points to. This can let an unprivileged user place malicious files in locations such as system configuration directories, potentially disrupting services. Run the module only with trusted user directories or update to a version that blocks symlink traversal.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
Ecosystem VendorProductAffected versions
– red hat red hat enterprise linux 10 All versions
– red hat red hat enterprise linux 9 All versions
Ubuntu:Pro:14.04:LTS canonical ansible All versions
Ubuntu:22.04:LTS canonical ansible-core All versions
Debian:12 debian ansible All versions
Original advisory text
Ansible.posix: authorized_key module follows a parent-directory symlink allowing writes outside the intended directory
A link-following flaw was found in the authorized_key module of the ansible.posix collection, residual to the fix for CVE-2026-11837. That fix guards only the final path component (os.chown with follow_symlinks=False and O_NOFOLLOW in _safe_open_write()). When an unprivileged local user replaces their ~/.ssh directory with a symlink to a directory they do not own, and an operator subsequently runs the authorized_key task as root (a common provisioning pattern), the module resolves its path operations through the symlink: atomic_move() writes the temporary file in the symlink target and renames it to <target>/authorized_keys, creating or overwriting a file in the attacker-chosen directory, and os.chmod(sshdir, 0o700) follows the symlink and changes the target directory's permissions. The written file is chowned to the unprivileged user, so this is not a privilege escalation, but it allows an attacker to create or overwrite files (for example in /etc/apt/apt.conf.d/, which APT reads regardless of file ownership) to cause integrity and availability impacts.
Fix within
Internet-facing 60 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker partial control
Severity
3.9 Low
Exploitation
<1% chance of attack within 30 days
Type
CWE-59Link Following
Timeline
Published12 Nov 2026
Updated17 Nov 2026
First seen12 Nov 2026
Track software like this
Free during beta