Ansible vulnerabilitiesRanked by how likely they are to be used.
Ansible is made by Red Hat. We track 45 published vulnerabilities listed under that exact name, across 361 versions. None of them is on the list of flaws known to be exploited today. Red Hat lists newer releases under their own names, such as Ansible Tower, so check those pages too.
We keep watching the known-exploited list.
Is Ansible listed under other names? Yes.
Red Hat also lists Ansible under more specific names, such as Ansible Tower and Ansible Engine. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
- Ansible Tower66 published vulnerabilities
- Ansible Engine27 published vulnerabilities
- Ansible Automation Platform23 published vulnerabilities
- Ansible Inside6 published vulnerabilities
- Ansible Developer6 published vulnerabilities
- Ansible Runner3 published vulnerabilities
- Ansible Automation Platform Early Access2 published vulnerabilities
- Ansible Collection2 published vulnerabilities
- Ansible Automation Controller1 published vulnerability
- Ansible Galaxy1 published vulnerability
- Ansible Automation Platform Text-Only Advisories1 published vulnerability
Which Ansible vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Ansible's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Ansible flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 17%CVE-2016-9587High
Ansible before versions 2.1.4, 2.2.1 is vulnerable to an improper input validation in Ansible's handling of data sent from client systems.
- 5.2%CVE-2014-4678Critical
The safe_eval function in Ansible before 1.6.4 does not properly restrict the code subset, which allows remote attackers to execute arbitrary code via crafted instructions.
- 4.4%CVE-2014-4657Critical
The safe_eval function in Ansible before 1.5.4 does not properly restrict the code subset, which allows remote attackers to execute arbitrary code via crafted instructions.
- 3.6%CVE-2017-7550Critical
A flaw was found in the way Ansible (2.3.x before 2.3.3, and 2.4.x before 2.4.1) passed certain parameters to the jenkins_plugin module.
- 3.5%CVE-2014-4966Critical
Ansible before 1.6.7 does not prevent inventory data with "{{" and "lookup" substrings, and does not prevent remote data with "{{" substrings, which allows remote attackers to execute arbitrary code via (1) crafted...
- 3.5%CVE-2014-4967Critical
Multiple argument injection vulnerabilities in Ansible before 1.6.7 allow remote attackers to execute arbitrary code by leveraging access to an Ansible managed host and providing a crafted fact, as demonstrated by a...
- 3.2%CVE-2016-8628Critical
Ansible before version 2.2.0 fails to properly sanitize fact variables sent from the Ansible controller.
- 3.1%CVE-2017-7466High
Ansible before version 2.3 has an input validation vulnerability in the handling of data sent from client systems.
- 2.5%CVE-2014-3498High
The user module in ansible before 1.6.6 allows remote authenticated users to execute arbitrary commands.
- 2.5%CVE-2018-16876Medium
ansible before versions 2.5.14, 2.6.11, 2.7.5 is vulnerable to a information disclosure flaw in vvv+ mode with no_log on that can lead to leakage of sensible data.
Running Ansible? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Ansible before versions 2.1.4, 2.2.1 is vulnerable to an improper input validation in Ansible's handling of data sent from client systems. An attacker with control over a client system being managed by Ansible and the ability to send facts back to the Ansible server could use this flaw to execute arbitrary code on the Ansible server using the Ansible server privileges.
- Matched to
- Ansible on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 45 published vulnerabilities listed under the name Ansible, across 361 versions.
None of Ansible's vulnerabilities is on the list of flaws known to be exploited today.
Red Hat also lists Ansible under more specific names, such as Ansible Tower and Ansible Engine. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Ansible. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.