CVE-2021-20180: PYSEC-2026-618 - Insertion of Sensitive Information into Log File in ansible

CVE-2021-20180 · Severity: low · CVSS 3.1 · Published 2026-07-02

Insertion of Sensitive Information into Log File in ansible

Technologies: ansible (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2021-20180 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2021-20180 being exploited in the wild.
How severe is CVE-2021-20180?
Low severity, with a CVSS score of 3.1, published 2 July 2026.
Which products and versions are affected?
ansible (PyPI) ECOSYSTEM:introduced=2.8.0a1,fixed=2.8.19, ECOSYSTEM:introduced=2.8.0a1,fixed=2.8.19,introduced=2.9.0b1,fixed=2.9.18.
Is there a fix for CVE-2021-20180?
Yes. ansible (PyPI): upgrade to 2.8.19, 2.9.18 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2021-20180?
Check whether you run ansible (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • ansible (PyPI): upgrade to 2.8.19, 2.9.18 or later
    pip install "ansible>=2.9.18"

Affected products

  • ansible (PyPI) ECOSYSTEM:introduced=2.8.0a1,fixed=2.8.19, ECOSYSTEM:introduced=2.8.0a1,fixed=2.8.19,introduced=2.9.0b1,fixed=2.9.18

Identifiers

  • CVE-2021-20180
  • GHSA-fh5v-5f35-2rv2
  • PYSEC-2026-618

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.