p PatchFirst

CVE-2026-11837

CVE-2026-11837 · Ansible-collection-ansible-posix: ansible.posix authorized_key: local privilege escalation via symlink-following chown

This page contains facts from public vulnerability sources. Check the original advisory before updating.

This page shows selected source facts. See the linked advisories for the complete description and affected versions.

A local privilege escalation vulnerability was found in the ansible.posix authorized_key module. The module's keyfile() function uses os.chown() instead of os.lchown() and opens files without O_NOFOLLOW when managing SSH authorized keys. An unprivileged local user can pre-stage symbolic links in their ~/.ssh directory to redirect file ownership changes to arbitrary system paths when an operator runs the authorized_key task as root, leading to local privilege escalation.

CVSS 7.3 · High · EPSS 0.2%

Published
Updated

Stack: system

Affected products and versions

  • red hat enterprise linux 10.0 extended update support

    Versions
    • ≥ 0:0.2.3-6.el10_0.2: Not affected (rpm)

    No fix published

  • red hat enterprise linux 8.6 advanced mission critical update support

    Versions
    • ≥ 0:0.1.8-2.el8_6.1: Not affected (rpm)

    No fix published

  • red hat enterprise linux 8.6 extended update support long-life add-on

    Versions
    • ≥ 0:0.1.8-2.el8_6.1: Not affected (rpm)

    No fix published

  • red hat enterprise linux 8.8 telecommunications update service

    Versions
    • ≥ 0:0.1.8-5.el8_8.1: Not affected (rpm)

    No fix published

  • red hat enterprise linux 8.8 update services for sap solutions

    Versions
    • ≥ 0:0.1.8-5.el8_8.1: Not affected (rpm)

    No fix published

  • red hat enterprise linux 10

    No fix published

  • red hat enterprise linux 10

    No fix published

  • red hat enterprise linux 8

    No fix published

  • red hat enterprise linux 8

    No fix published

  • red hat enterprise linux 9

    No fix published

  • red hat enterprise linux 9

    No fix published

  • red hat openstack platform 17.1

    No fix published

  • red hat openstack platform 18.0

    No fix published

  • ansible Debian:12

    Versions
    • 10.0.0+dfsg-1
    • 10.0.1+dfsg-1
    • 10.1.0+dfsg-1
    • 10.5.0+dfsg-1
    • 10.5.0+dfsg-2
    • 10.6.0+dfsg-1
    • 11.1.0+dfsg-1
    • 11.2.0+dfsg-1
    • 12.0.0+dfsg-1
    • 12.0.0~a1+dfsg-1
    • 12.0.0~a2+dfsg-1
    • 12.0.0~a4+dfsg-1
    • 12.0.0~a6+dfsg-1
    • 12.0.0~b1+dfsg-1
    • 12.0.0~b2+dfsg-1
    • 12.0.0~b3+dfsg-1
    • 12.0.0~b5+dfsg-1
    • 12.2.0+dfsg-1
    • 13.1.0+dfsg-1
    • 13.4.0+dfsg-1
    • 14.0.0+dfsg-1
    • 14.0.0~a4+dfsg-1
    • 14.4.0+dfsg-1
    • 7.3.0+dfsg-1
    • 7.7.0+dfsg-1
    • 7.7.0+dfsg-2
    • 7.7.0+dfsg-3
    • 7.7.0+dfsg-3+deb12u1
    • 9.4.0+dfsg-1
    • 9.5.1+dfsg-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Debian:13

    Versions
    • 12.0.0+dfsg-0+deb13u1
    • 12.0.0+dfsg-1
    • 12.0.0~a6+dfsg-1
    • 12.0.0~b1+dfsg-1
    • 12.0.0~b2+dfsg-1
    • 12.0.0~b3+dfsg-1
    • 12.0.0~b5+dfsg-0+deb13u1
    • 12.0.0~b5+dfsg-1
    • 12.2.0+dfsg-1
    • 13.1.0+dfsg-1
    • 13.4.0+dfsg-1
    • 14.0.0+dfsg-1
    • 14.0.0~a4+dfsg-1
    • 14.4.0+dfsg-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Debian:14

    Versions
    • 12.0.0+dfsg-1
    • 12.0.0~a6+dfsg-1
    • 12.0.0~b1+dfsg-1
    • 12.0.0~b2+dfsg-1
    • 12.0.0~b3+dfsg-1
    • 12.0.0~b5+dfsg-1
    • 12.2.0+dfsg-1
    • 13.1.0+dfsg-1
    • 13.4.0+dfsg-1
    • 14.0.0+dfsg-1
    • 14.0.0~a4+dfsg-1
    • 14.4.0+dfsg-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Ubuntu:Pro:14.04:LTS

    Versions
    • 1.1+dfsg-1
    • 1.3.4+dfsg-1
    • 1.4.0+dfsg-1
    • 1.4.1+dfsg-1
    • 1.4.3+dfsg-1
    • 1.4.4+dfsg-1
    • 1.5.4+dfsg-1
    • 1.5.4+dfsg-1ubuntu0.1~esm1
    • 1.5.4+dfsg-1ubuntu0.1~esm2
    • 1.5.4+dfsg-1ubuntu0.1~esm3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Ubuntu:Pro:16.04:LTS

    Versions
    • 1.9.2+dfsg-2
    • 1.9.4-1
    • 2.0.0.2-2
    • 2.0.0.2-2ubuntu1
    • 2.0.0.2-2ubuntu1.1
    • 2.0.0.2-2ubuntu1.2
    • 2.0.0.2-2ubuntu1.3
    • 2.0.0.2-2ubuntu1.3+esm1
    • 2.0.0.2-2ubuntu1.3+esm2
    • 2.0.0.2-2ubuntu1.3+esm3
    • 2.0.0.2-2ubuntu1.3+esm4
    • 2.0.0.2-2ubuntu1.3+esm5
    • 2.0.0.2-2ubuntu1.3+esm6
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Ubuntu:Pro:18.04:LTS

    Versions
    • 2.3.1.0+dfsg-2
    • 2.5.0+dfsg-1
    • 2.5.1+dfsg-1
    • 2.5.1+dfsg-1ubuntu0.1
    • 2.5.1+dfsg-1ubuntu0.1+esm1
    • 2.5.1+dfsg-1ubuntu0.1+esm2
    • 2.5.1+dfsg-1ubuntu0.1+esm3
    • 2.5.1+dfsg-1ubuntu0.1+esm4
    • 2.5.1+dfsg-1ubuntu0.1+esm5
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Ubuntu:Pro:20.04:LTS

    Versions
    • 2.8.3+dfsg-1
    • 2.8.6+dfsg-1
    • 2.9.2+dfsg-1
    • 2.9.4+dfsg-1
    • 2.9.6+dfsg-1
    • 2.9.6+dfsg-1ubuntu0.1~esm1
    • 2.9.6+dfsg-1ubuntu0.1~esm2
    • 2.9.6+dfsg-1ubuntu0.1~esm3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible-core Ubuntu:22.04:LTS

    Versions
    • 2.12.0-1
    • 2.12.0-1ubuntu0.1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Ubuntu:Pro:22.04:LTS

    Versions
    • 2.10.7+merged+base+2.10.8+dfsg-1
    • 2.10.7+merged+base+2.10.8+dfsg-1ubuntu0.1~esm1
    • 2.10.7+merged+base+2.10.8+dfsg-1ubuntu0.1~esm4
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible Ubuntu:24.04:LTS

    Versions
    • 7.7.0+dfsg-1
    • 7.7.0+dfsg-3
    • 9.2.0+dfsg-0ubuntu4
    • 9.2.0+dfsg-0ubuntu5
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • ansible-core Ubuntu:24.04:LTS

    Versions
    • 2.14.9-2
    • 2.14.11-1
    • 2.14.11-2
    • 2.14.13-1
    • 2.16.3-0ubuntu1
    • 2.16.3-0ubuntu2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →