CVE-2019-3828: Path Traversal Vulnerability in Ansible
Summary
CVE-2019-3828: Ansible Path Traversal vulnerability. Affects ansible across 3 version ranges.
< 2.5.15
>= 2.6.0a1, < 2.6.14
>= 2.7.0a1, < 2.7.8
Fixed in 2.5.15, 2.6.14 or 2.7.8, depending on the release line you run. How to fix ↓
Also tracked for
- ansible · Alpine:v3.10
The same CVE-2019-3828 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 IT tasks such as configuration management, application deployment, and orchestration. It is widely used in the DevOps community for its simplicity and flexibility. However, Ansible versions prior to 2.5.15, 2.6.14, and 2.7.8 are vulnerable to a path traversal vulnerability. This vulnerability enables an attacker to copy and overwrite files outside of the specified destination on the local Ansible controller host.
Vulnerability Detail
The path traversal vulnerability in Ansible arises from the lack of proper limitation on a pathname to a restricted directory. By not restricting an absolute path, an attacker can exploit this vulnerability to access and modify files outside of the intended destination. This can lead to unauthorized access, data leakage, and potential compromise of the Ansible controller host.
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.5.152.5.15pip install --upgrade "ansible==2.5.15" -
>= 2.6.0a1, < 2.6.142.6.14pip install --upgrade "ansible==2.6.14" -
>= 2.7.0a1, < 2.7.82.7.8pip install --upgrade "ansible==2.7.8"
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 known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading to the fixed versions of Ansible.
Conclusion
The path traversal vulnerability in Ansible can lead to unauthorized access, data leakage, and potential compromise of the system. It is crucial to upgrade to the fixed versions of Ansible (2.5.15, 2.6.14, or 2.7.8) to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for ansible →
FAQ
This vulnerability allows an attacker to access and modify files outside of the intended destination on the local Ansible controller host. It can lead to unauthorized access, data leakage, and potential compromise of the system.
No, only Ansible versions prior to 2.5.15, 2.6.14, and 2.7.8 are affected by this vulnerability. It is recommended to upgrade to the fixed versions to mitigate the risk.
There is no known public exploit for this vulnerability at the moment. However, it is crucial to apply the recommended fix to prevent any potential exploitation.
No, this vulnerability can only be exploited by an attacker with access to the local Ansible controller host.
There is no evidence of active exploitation of this vulnerability at the moment. However, it is still recommended to apply the fix as a proactive security measure.
References
Related vulnerabilities
Recent vulnerabilities recorded for ansible.
