CVE-2019-10156: Information Disclosure in ansible
Summary
CVE-2019-10156: Exposure of Sensitive Information to an Unauthorized Actor in ansible. Affects ansible across 3 version ranges.
< 2.6.18
>= 2.7.0a1, < 2.7.12
>= 2.8.0a1, < 2.8.2
Fixed in 2.6.18, 2.7.12 or 2.8.2, depending on the release line you run. How to fix ↓
Also tracked for
- ansible · Alpine:v3.10
The same CVE-2019-10156 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Ansible is an open-source automation tool that allows users to automate tasks such as configuration management, application deployment, and orchestration. It uses a simple and human-readable language called YAML to define automation tasks. Ansible is widely used in the IT industry for managing infrastructure and deploying applications.
Vulnerability Detail
A vulnerability was discovered in Ansible versions before 2.6.18, 2.7.12, and 2.8.2. This vulnerability allows an unauthorized actor to access sensitive information through unexpected variable substitution in Ansible templating. By exploiting unintended variable substitution, an attacker can disclose the content of any variable, potentially exposing sensitive data.
How To Fix
Latest published version: 14.5.0 as of 22 Oct 2026
pip install --upgrade "ansible==14.5.0"Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 2.6.182.6.18pip install --upgrade "ansible==2.6.18" -
>= 2.7.0a1, < 2.7.122.7.12pip install --upgrade "ansible==2.7.12" -
>= 2.8.0a1, < 2.8.22.8.2pip install --upgrade "ansible==2.8.2"
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. The recommended solution is to upgrade to the fixed versions of Ansible.
Conclusion
In conclusion, the vulnerability in Ansible versions before 2.6.18, 2.7.12, and 2.8.2 allows unauthorized access to sensitive information. It is crucial to upgrade to the fixed versions to mitigate the risk of information disclosure. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for ansible →
FAQ
Ansible is an open-source automation tool used for configuration management, application deployment, and orchestration.
This vulnerability allows an unauthorized actor to access sensitive information through unintended variable substitution in Ansible templating.
To fix this vulnerability, you should upgrade to Ansible 2.6.18, 2.7.12, or 2.8.2, depending on your current version.
There is no specific workaround mentioned for this vulnerability. Upgrading to the fixed versions is the recommended solution.
You can find more information about this vulnerability in the provided sources: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2019/07/GHSA-grgm-pph5-j5h7/GHSA-grgm-pph5-j5h7.json
References
Related vulnerabilities
Recent vulnerabilities recorded for ansible.
