VYPR
High severity7.3NVD Advisory· Published Jun 10, 2026

CVE-2026-11837

CVE-2026-11837

Description

Ansible.posix authorized_key module allows local privilege escalation via symlink following in chown operations.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Ansible.posix authorized_key module allows local privilege escalation via symlink following in chown operations.

Vulnerability

A local privilege escalation vulnerability exists in the ansible.posix authorized_key module. The keyfile() function incorrectly uses os.chown() instead of os.lchown() and opens files without the O_NOFOLLOW flag when managing SSH authorized keys. This affects versions of the ansible.posix collection where this behavior is present.

Exploitation

An unprivileged local user can exploit this vulnerability by creating symbolic links within their ~/.ssh directory. When an operator executes an authorized_key task as root, the module will follow these symbolic links. This allows the user to manipulate ownership of arbitrary system files or directories by tricking the chown operation into targeting them instead of the intended authorized_keys file.

Impact

Successful exploitation allows an unprivileged local user to escalate their privileges to root. By controlling the ownership of critical system files or directories, an attacker can potentially gain complete control over the affected system.

Mitigation

This vulnerability is addressed in a fixed version of the ansible.posix collection. Users should update to the patched version as soon as possible. No specific version or release date for the fix is provided in the available references, but the issue is noted as fixed in reference [2].

AI Insight generated on Jun 10, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

2

News mentions

0

No linked articles in our index yet.