Is ansible-core 2.20 vulnerable?
PyPI · 12 releases from 2.20.0 to 2.20.11 · latest ansible-core is 2.22.0 · checked 18 Nov 2026
No known advisories in the last release
ansible-core 2.20.11, the last 2.20 release, has no known advisories. 1 advisory affects earlier 2.20.x releases, so update to 2.20.11.
pip install 'ansible-core>=2.20.11'Is your project on an affected ansible-core?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 2.20.x, affecting earlier releases
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
Every ansible-core 2.20.x release
Affected: 2.20.0 to 2.20.6. 2.20.7 and later are not affected. Latest ansible-core: 2.22.0.
| Version | Known advisories |
|---|---|
| ansible-core 2.20.11 | None |
| ansible-core 2.20.10 | None |
| ansible-core 2.20.9 | None |
| ansible-core 2.20.8 | None |
| ansible-core 2.20.7 | None |
| ansible-core 2.20.6 | CVE-2026-11332 |
| ansible-core 2.20.5 | CVE-2026-11332 |
| ansible-core 2.20.4 | CVE-2026-11332 |
| ansible-core 2.20.3 | CVE-2026-11332 |
| ansible-core 2.20.2 | CVE-2026-11332 |
| ansible-core 2.20.1 | CVE-2026-11332 |
| ansible-core 2.20.0 | CVE-2026-11332 |
Which of your client projects are still on ansible-core 2.20?
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.