Is ansible-core 2.17 vulnerable?

PyPI · 15 releases from 2.17.0 to 2.17.14 · latest ansible-core is 2.22.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. ansible-core 2.17.14, the last 2.17 release, is affected by 1 known security advisory (1 high), including CVE-2026-11332. 3 more affect earlier 2.17.x releases. Upgrade to 2.18.18rc1 or later to fix all of them.

Upgrade with:pip install 'ansible-core>=2.18.18rc1'

Is your project on an affected ansible-core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting ansible-core 2.17.14

  • HighCVE-2026-11332GHSA-w8p5-mx5w-cpqj5 Jun 2026

    ansible-core: Argument injection in ansible-galaxy role install leads to arbitrary code execution

    Affected
    <2.16.19rc1 · >=2.17.0b1 <2.18.18rc1 · >=2.19.0b1 <2.19.11rc1 · >=2.20.0b1 <2.20.7rc1 · >=2.21.0b1 <2.21.1rc1
    Fixed in
    2.16.19rc1, 2.18.18rc1, 2.19.11rc1, 2.20.7rc1, 2.21.1rc1

Fixed within 2.17.x, affecting earlier releases

  • LowCVE-2024-11079GHSA-99w6-3xph-cx7812 Nov 2024

    Ansible-Core vulnerable to content protections bypass

    Affected
    >=2.18.0b1 <2.18.1rc1 · >=2.17.0b1 <2.17.7rc1 · <2.16.14rc1
    Fixed in
    2.16.14rc1, 2.17.7rc1, 2.18.1rc1
  • MediumCVE-2024-9902GHSA-32p4-gm2c-wmch6 Nov 2024

    ansible-core Incorrect Authorization vulnerability

    Affected
    <2.14.18rc1 · >=2.15.0b1 <2.15.13rc1 · >=2.16.0b1 <2.16.13rc1 · >=2.17.0b1 <2.17.6rc1 · >=2.18.0b1 <2.18.0rc2
    Fixed in
    2.14.18rc1, 2.15.13rc1, 2.16.13rc1, 2.17.6rc1, 2.18.0rc2
  • HighCVE-2024-8775GHSA-jpxc-vmjf-9fcj16 Sept 2024

    Ansible vulnerable to Insertion of Sensitive Information into Log File

    Affected
    >=2.17.0b1 <2.17.6 · <2.16.13
    Fixed in
    2.16.13, 2.17.6

Every ansible-core 2.17.x release

Affected: 2.17.0 to 2.17.14. Latest ansible-core: 2.22.0.

VersionKnown advisories
ansible-core 2.17.14CVE-2026-11332
ansible-core 2.17.13CVE-2026-11332
ansible-core 2.17.12CVE-2026-11332
ansible-core 2.17.11CVE-2026-11332
ansible-core 2.17.10CVE-2026-11332
ansible-core 2.17.9CVE-2026-11332
ansible-core 2.17.8CVE-2026-11332
ansible-core 2.17.7CVE-2026-11332
ansible-core 2.17.6CVE-2026-11332, CVE-2024-11079
ansible-core 2.17.5CVE-2026-11332, CVE-2024-11079, CVE-2024-9902, CVE-2024-8775
ansible-core 2.17.4CVE-2026-11332, CVE-2024-11079, CVE-2024-9902, CVE-2024-8775
ansible-core 2.17.3CVE-2026-11332, CVE-2024-11079, CVE-2024-9902, CVE-2024-8775
ansible-core 2.17.2CVE-2026-11332, CVE-2024-11079, CVE-2024-9902, CVE-2024-8775
ansible-core 2.17.1CVE-2026-11332, CVE-2024-11079, CVE-2024-9902, CVE-2024-8775
ansible-core 2.17.0CVE-2026-11332, CVE-2024-11079, CVE-2024-9902, CVE-2024-8775

Which of your client projects are still on ansible-core 2.17?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact ansible-core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other ansible-core versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.