Ansible vulnerabilities: known CVEs & security history
Red Hat · Automation / DevOps · 45 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Ansible release lines — 45 in total. A CVE here doesn't mean your version is affected — check Ansible's current status and the safe version to run.
Known Ansible CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2014-4657 | critical | 9.8 | 4% | 2020 |
| CVE-2014-4678 | critical | 9.8 | 5% | 2020 |
| CVE-2014-4967 | critical | 9.8 | 3% | 2020 |
| CVE-2014-4966 | critical | 9.8 | 3% | 2020 |
| CVE-2017-7550 | critical | 9.8 | 4% | 2017 |
| CVE-2014-3498 | high | 8.8 | 2% | 2017 |
| CVE-2016-9587 | high | 8.1 | 18% | 2018 |
| CVE-2017-7466 | high | 8 | 3% | 2018 |
| CVE-2020-10684 | high | 7.9 | 0% | 2020 |
| CVE-2015-6240 | high | 7.8 | 0% | 2017 |
| CVE-2016-3096 | high | 7.8 | 0% | 2016 |
| CVE-2016-8628 | high | 7.6 | 3% | 2018 |
| CVE-2022-3697 | high | 7.5 | 1% | 2022 |
| CVE-2014-2686 | high | 7.5 | 1% | 2020 |
| CVE-2013-2233 | high | 7.4 | 2% | 2018 |
| CVE-2019-14904 | high | 7.3 | 0% | 2020 |
| CVE-2023-5764 | high | 7.1 | 1% | 2023 |
| CVE-2020-25636 | medium | 6.6 | 0% | 2020 |
| CVE-2019-14864 | medium | 6.5 | 2% | 2020 |
| CVE-2019-14856 | medium | 6.5 | 2% | 2019 |
| CVE-2019-10217 | medium | 6.5 | 2% | 2019 |
| CVE-2019-10206 | medium | 6.5 | 2% | 2019 |
| CVE-2016-8614 | medium | 6.3 | 2% | 2018 |
| CVE-2021-20180 | medium | 5.5 | 0% | 2022 |
| CVE-2021-20191 | medium | 5.5 | 0% | 2021 |
| CVE-2021-20178 | medium | 5.5 | 0% | 2021 |
| CVE-2021-3447 | medium | 5.5 | 0% | 2021 |
| CVE-2014-4659 | medium | 5.5 | 0% | 2020 |
| CVE-2014-4658 | medium | 5.5 | 0% | 2020 |
| CVE-2014-4660 | medium | 5.5 | 0% | 2020 |
| CVE-2019-10156 | medium | 5.4 | 2% | 2019 |
| CVE-2018-16876 | medium | 5.3 | 2% | 2019 |
| CVE-2024-0690 | medium | 5 | 0% | 2024 |
| CVE-2020-25635 | medium | 5 | 0% | 2020 |
| CVE-2020-10744 | medium | 5 | 0% | 2020 |
| CVE-2020-1733 | medium | 5 | 0% | 2020 |
| CVE-2015-3908 | medium | 4.3 | 1% | 2015 |
| CVE-2020-1735 | medium | 4.2 | 0% | 2020 |
| CVE-2019-3828 | medium | 4.2 | 1% | 2019 |
| CVE-2020-1740 | low | 3.9 | 0% | 2020 |
| CVE-2020-1738 | low | 3.9 | 0% | 2020 |
| CVE-2020-1739 | low | 3.9 | 0% | 2020 |
| CVE-2013-4260 | low | 3.3 | 0% | 2013 |
| CVE-2020-1736 | low | 2.2 | 0% | 2020 |
| CVE-2013-4259 | low | 1.9 | 0% | 2013 |
Is my Ansible version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Ansible version → · Monitor Ansible for new CVEs →
Ansible vulnerabilities — frequently asked
How many known vulnerabilities does Ansible have?
IsItPatched tracks 45 CVEs for Ansible. 5 are critical-severity and 12 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Ansible have any actively-exploited vulnerabilities?
None of Ansible's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe Ansible vulnerability?
Among tracked issues, CVE-2014-4657 (CRITICAL, CVSS 9.8) ranks highest — a Improper input validation weakness.
Is Ansible safe to use?
It depends on the version. The latest supported Ansible release (14.0.0) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Ansible security status · Ansible end-of-life · actively-exploited CVEs. Always verify against Red Hat's advisories — see our disclaimer.