CVE-2021-20178: Sensitive Information Disclosure in ansible

ansible Updated 02 Oct 2025

Summary

01/06/2021
Yes i
High
5.5

CVE-2021-20178: Insertion of Sensitive Information into Log File in ansible. Affects ansible versions < 2.9.18. Fixed in 2.9.18. How to fix ↓

Also tracked for

The same CVE-2021-20178 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Ansible is an open-source automation tool that allows users to automate tasks such as configuration management, application deployment, and orchestration. It is widely used in IT infrastructure management and provides a simple and powerful way to automate complex tasks. However, a vulnerability has been discovered in the ansible module that can lead to the disclosure of sensitive information.

Vulnerability Detail

The vulnerability, identified as CVE-2021-20178, involves the insertion of sensitive information into a log file in ansible. By default, credentials are disclosed in the console log and are not protected by the security feature when using the bitbucket_pipeline_variable module. This flaw can be exploited by an attacker to steal bitbucket_pipeline credentials, potentially compromising the confidentiality of the system. The vulnerability has a CVSS score of 5.5, indicating a moderate severity level.

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 version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.9.18

This is the first release that contains the fix.

pip install --upgrade "ansible==2.9.18"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended solution is to update ansible to the latest version.

Conclusion

In conclusion, the CVE-2021-20178 vulnerability in ansible exposes sensitive information in the console log, potentially leading to the theft of bitbucket_pipeline credentials. Users are advised to update their ansible installation to version 2.9.18 or later to mitigate this risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for ansible →

Share this vulnerability

FAQ

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

This vulnerability allows an attacker to steal bitbucket_pipeline credentials, potentially compromising the confidentiality of the system.

The CVSS score of this vulnerability is 5.5, indicating a moderate severity level.

To fix this vulnerability, update ansible to version 2.9.18 or later.

There is no specific workaround mentioned for this vulnerability. Updating ansible to the latest version is the recommended solution.

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 version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.9.18

This is the first release that contains the fix.

pip install --upgrade "ansible==2.9.18"

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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