© 2025-2026 PySpect
First version without a known vulnerability: 13.0.0a1
Ansible Community General Collection is vulnerable to exposure of sensitive information
Fixed in: 12.2.0
Ansible does not collect garbage after playbook run
Fixed in: 2.10.1
Ansible symlink attack vulnerability
Fixed in: 8.5.0
Ansible leaks password to logs
Fixed in: 7.0.0
Ansible Exposes Sensitive Information
Fixed in: 2.10.6rc1, 2.9.18rc1, 2.8.19rc1, 2.9.19
Ansible Code Injection Vulnerability
Fixed in: 1.6.4, 5429b85b9f6c2e640074176f36ff05fd5e4d1916
Ansible password prompts could expose passwords
Fixed in: 2.8.6, 2.7.14, 2.6.20
Ansible password prompts could expose passwords
Fixed in: 2.8.4, 2.7.13, 2.6.19
Ansible leaks sensitive information to logs when told not to
Fixed in: 2.9.0rc4, 2.8.6, 2.7.14, 2.6.20, 2.8.1
Ansible Uses Plugins That Disclose Credentials
Fixed in: 2.6.20, 2.7.14, 2.8.6
Ansible Sensitive Files Are Locally Readable
Fixed in: 1.5.5
Ansible discloses credential information
Fixed in: 1.5.5, c4b5e46054c74176b2446c82d4df1a2610eddc08
Ansible sets unsafe permissions for sources.list
Fixed in: 1.5.5
Ansible Remote Code Execution
Fixed in: 1.5.4
Ansible Arbitrary Code Execution
Fixed in: 1.6.7, 62a1295a3e08cb6c3e9f1b2a1e6e5dcaeab32527
Ansible Arbitrary Code Execution
Fixed in: 1.6.7, 62a1295a3e08cb6c3e9f1b2a1e6e5dcaeab32527
Ansible unsafe evaluation of some strings
Fixed in: 1.5.4
Ansible Arbitrary Code Execution
Fixed in: 1.6.6, 8ed6350e65c82292a631f08845dfaacffe7f07f5
Ansible uses a socket with predictable filename in /tmp
Fixed in: 1.2.3
Ansible Arbitrary File Overwrite Vulnerability
Fixed in: 1.2.3
Ansible Logs Passwords If PowerShell ScriptBlock is Enabled
Fixed in: 2.7.3, 2.5.12, 2.6.9, 2.7.4, 2.8.1, 2.5.13, 2.6.10
Ansible Sandbox Escape via Symlink Attack
Fixed in: 1.9.2, ca2f2c4ebd7b5e097eab0a710f79c1f63badf95b, 952166f48eb0f5797b75b160fd156bbe1e8fc647
Ansible Leaks Data Passed to ssh-keygen
Fixed in: 2.7.1, 2.6.7, 2.5.11
Ansible Arbitrary Code Execution
Fixed in: 2.4.6.0, 2.5.6, 2.6.1
Ansible Improper Input Validation vulnerability
Fixed in: 2.4.6.0, 2.5.6, 2.6.1
Ansible sensitive information disclosure
Fixed in: 2.5.14, 2.6.11, 2.7.5
Ansible Arbitrary Code Execution
Fixed in: 2.2.3.0, 2.3.0.0
Ansible Insertion of Sensitive Information into Log File vulnerability
Fixed in: 2.4.1.0, 2.3.3.0
Insertion of Sensitive Information into Log File in ansible
Fixed in: 2.8.19, 2.9.18
Ansible discloses sensitive information in traceback error message
Fixed in: 2.9.27, fe28767970c8ec62aabe493c46b53a5de1e5fac0
Improper Output Neutralization and Improper Encoding or Escaping of Output for Logs in ansible
Fixed in: 2.10.0
Argument Injection in Ansible
Fixed in: 2.7.17, 2.8.9, 2.9.6
Incorrect Permission Assignment for Critical Resource in Ansible
Fixed in: 2.7.17, 2.8.9, 2.9.6
Exposure of Resource to Wrong Sphere and Insecure Temporary File in Ansible
Fixed in: 2.10.0rc1, 2.9.12, 2.8.0a1, 2.8.13, 2.9.10
Insertion of Sensitive Information into Log File and Improper Output Neutralization for Logs in ansible
Fixed in: 2.8.14, 2.9.12, 2.10.1rc2
OS Command Injection in ansible
Fixed in: 2.10.0rc1, 2.9.11, 2.8.13, 2.7.17
Exposure of Sensitive Information to an Unauthorized Actor in ansible
Fixed in: 2.8.4
Improper Input Validation and Command Injection in Ansible
Fixed in: 2.9.23rc1, 2.10.11rc1, 2.11.2rc1, 2.9.23
Insufficiently random values in Ansible
Fixed in: 2.9.6
A flaw was found in Ansible if an ansible user sets ANSIBLE_ASYNC_DIR to a subdirectory of a world writable directory. When this occurs, there is a race condition on the managed machine. A malicious, non-privileged account on the remote machine can exploit the race condition to access the async result data. This flaw affects Ansible Tower 3.7 and Ansible Automation Platform 1.2.
Fixed in: 3.0.0
Insertion of Sensitive Information into Log File in ansible
Fixed in: 2.9.18
Insertion of Sensitive Information into Log File in ansible
Fixed in: 2.9.18rc1, 2.8.19rc1, 2.10.7, 2.8.19, 2.9.18
Ansible vulnerable to Exposure of Resource to Wrong Sphere and Insecure Temporary File
Fixed in: 2.7.17, 2.8.11, 2.9.7, 2.8.8, 2.9.6
Externally Controlled Reference to a Resource in Another Sphere, Improper Input Validation, and External Control of File Name or Path in Ansible
Fixed in: 2.7.16, 2.8.8, 2.9.3
Path Traversal in Ansible
Fixed in: 2.9.7
OS Command Injection and Improper Input Validation in ansible
Fixed in: 2.7.16, 2.8.8, 2.9.3, 2.7.15, 2.8.7, 2.9.2
Improper Verification of Cryptographic Signature in ansible
Fixed in: 2.8.15, 2.9.13, 2.8.16rc1, 2.9.14rc1
Exposure of Sensitive Information to an Unauthorized Actor in ansible
Fixed in: 2.8.11, 2.9.7, 2.7.17
Path Traversal in Ansible
Fixed in: 2.8.9, 2.9.6, 2.7.17
Exposure of Sensitive Information to an Unauthorized Actor and Insecure Temporary File in Ansible
Fixed in: 2.7.17, 2.8.11, 2.9.7, 2.8.9, 2.9.6
Code Injection, Race Condition, and Execution with Unnecessary Privileges in Ansible
Fixed in: 2.7.17, 2.8.11, 2.9.7, 2.8.9, 2.9.6
Exposure of Resource to Wrong Sphere and Insecure Temporary File in Ansible
Fixed in: 2.7.17, 2.8.11, 2.9.7
Path Traversal in Ansible
Fixed in: 2.7.18, 2.8.12, 2.9.8, 2.7.17, 2.8.9, 2.9.6
Insertion of Sensitive Information into Log File, Invocation of Process Using Visible Sensitive Information, and Exposure of Sensitive Information to an Unauthorized Actor in Ansible
Fixed in: 2.7.18, 2.8.12, 2.9.7, 2.8.11
Exposure of Sensitive Information to an Unauthorized Actor in Ansible
Fixed in: 2.7.17, 2.8.11, 2.9.7, 2.8.9, 2.9.6
A flaw was found in several ansible modules, where parameters containing credentials, such as secrets, were being logged in plain-text on managed nodes, as well as being made visible on the controller node when run in verbose mode. These parameters were not protected by the no_log feature. An attacker can take advantage of this information to steal those credentials, provided when they have access to the log files containing them. The highest threat from this vulnerability is to data confidentiality. This flaw affects Red Hat Ansible Automation Platform in versions before 1.2.2 and Ansible Tower in versions before 3.8.2.
Fixed in: 1.2.2
Inclusion of Sensitive Information in Log Files and Improper Output Neutralization for Logs in Ansible
Fixed in: 2.7.15, 2.8.7, 2.9.1
Exposure of Sensitive Information to an Unauthorized Actor in ansible
Fixed in: 2.6.18, 2.7.12, 2.8.2
Ansible Path Traversal vulnerability
Fixed in: 2.5.15, 2.6.14, 2.7.8
Ansible does not verify that the server hostname matches a domain name in certificates
Fixed in: 1.9.2
Link Following in ansible
Fixed in: 2.0.2.0, 1.9.6.1
Ansible fails to cache SSH host keys
Fixed in: 1.2.1
Improper Input Validation in ansible
Fixed in: 2.2.1.0
Ansible apt_key module does not properly verify key fingerprint
Fixed in: 2.2.0.0
Ansible exposes sensitive data in log files and on the terminal
Fixed in: 2.5.5, 2.4.5.0
Ansible fails to properly sanitize fact variables sent from the Ansible controller
Fixed in: 2.2.0.0
Ansible is vulnerable to an improper input validation in Ansible's handling of data sent from client systems
Fixed in: 2.1.4.0, 2.2.1.0
Ansible fails to properly mark lookup-plugin results as unsafe
Fixed in: 2.3.1.0, 2.1.6.0, 2.2.3.0, ed56f51f185a1ffd7ea57130d260098686fcc7c2, 2.4.0.0