CVE-2020-1736: Ansible Engine File Mode Disclosure Vulnerability
Summary
CVE-2020-1736: A flaw was found in Ansible Engine when a file is moved using atomic_move primitive as the file mode cannot be specified. Affects ansible across 3 version ranges.
< 2.7.17
>= 2.8.0, < 2.8.9
>= 2.9.0, < 2.9.6
Fixed in 2.7.17, 2.8.9 or 2.9.6, depending on the release line you run. How to fix ↓
Also tracked for
- ansible · Debian:11
The same CVE-2020-1736 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 Engine is an open-source automation platform that allows users to automate IT tasks such as configuration management, application deployment, and orchestration. It is widely used in the industry due to its simplicity and flexibility. However, a vulnerability has been discovered in Ansible Engine that could lead to the disclosure of sensitive data.
Vulnerability Detail
The vulnerability (CVE-2020-1736) exists in Ansible Engine when a file is moved using the atomic_move primitive without specifying the file mode. This flaw allows an attacker to set the destination files as world-readable if the destination file does not exist. Additionally, if the file already exists, the attacker can change its permissions to have less restrictive settings before the move. As a result, sensitive data could be exposed to unauthorized users. This vulnerability affects all versions in the 2.7.x, 2.8.x, and 2.9.x branches of Ansible Engine.
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.7.172.7.17pip install --upgrade "ansible==2.7.17" -
>= 2.8.0, < 2.8.92.8.9pip install --upgrade "ansible==2.8.9" -
>= 2.9.0, < 2.9.62.9.6pip install --upgrade "ansible==2.9.6"
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 fixes as soon as possible.
Conclusion
The vulnerability in Ansible Engine (CVE-2020-1736) could result in the disclosure of sensitive data. It is crucial to update to the fixed versions mentioned above to mitigate this risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for ansible →
FAQ
Ansible Engine is an open-source automation platform used for IT tasks such as configuration management and application deployment.
This vulnerability could lead to the disclosure of sensitive data to unauthorized users.
All versions in the 2.7.x, 2.8.x, and 2.9.x branches of Ansible Engine are believed to be vulnerable.
No, there are no known workarounds for this vulnerability. Updating to the fixed versions is the recommended solution.
You can find more information about this vulnerability in the official advisory database: https://github.com/pypa/advisory-database/blob/main/vulns/ansible/PYSEC-2020-8.yaml
Related vulnerabilities
Recent vulnerabilities recorded for ansible.
