CVE-2020-14332: Ansible Engine module_args Sensitive Data Exposure

ansible Updated 02 Oct 2025

Summary

11/09/2020
Yes i
Moderate
5.5

CVE-2020-14332: A flaw was found in the Ansible Engine when using module_args. Affects ansible across 2 version ranges.

>= 2.8.0, < 2.8.14 >= 2.9.0, < 2.9.12

Fixed in 2.8.14 or 2.9.12, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2020-14332 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

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 provides a simple and powerful way to automate repetitive tasks, streamline workflows, and improve productivity. However, a vulnerability has been discovered in Ansible Engine related to the handling of module_args. This vulnerability can lead to the exposure of sensitive data and unauthorized access to this data.

Vulnerability Detail

The flaw in Ansible Engine occurs when using module_args. When tasks are executed in check mode (--check-mode), sensitive data exposed in the event data is not properly neutralized. This means that unauthorized users can read this data, potentially compromising the confidentiality of the system. The vulnerability affects versions 2.8.0 to 2.8.14 and 2.9.0 to 2.9.12 of the Ansible package.

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.8.0, < 2.8.14 2.8.14
    pip install --upgrade "ansible==2.8.14"
  • >= 2.9.0, < 2.9.12 2.9.12
    pip install --upgrade "ansible==2.9.12"

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. It is advised to apply the fix by upgrading to the patched versions of Ansible.

Conclusion

The vulnerability in Ansible Engine related to module_args can result in the exposure of sensitive data and unauthorized access. It is crucial to upgrade to the fixed versions of Ansible (2.8.15 or later for versions 2.8.0 to 2.8.14, and 2.9.13 or later for versions 2.9.0 to 2.9.12) to ensure the security and confidentiality of your system. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for ansible →

Share this vulnerability

FAQ

Ansible Engine is an open-source automation platform used for configuration management, application deployment, and orchestration.

module_args is a parameter used in Ansible tasks to pass arguments to modules. It allows users to customize the behavior of modules.

Check mode is a feature in Ansible that allows users to simulate the execution of tasks without making any changes. It is often used for testing and validation purposes.

This vulnerability can lead to the exposure of sensitive data in Ansible event data. Unauthorized users can read this data, potentially compromising the confidentiality of the system.

You can use the Vulert playground (https://vulert.com/scanner) to check if your Ansible version is affected by this vulnerability. Simply upload your Pipfile.lock and it will alert you in real-time.

Related vulnerabilities

Recent vulnerabilities recorded for ansible.

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.8.0, < 2.8.14 2.8.14
    pip install --upgrade "ansible==2.8.14"
  • >= 2.9.0, < 2.9.12 2.9.12
    pip install --upgrade "ansible==2.9.12"

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback