CVE-2021-20191: A flaw was found in ansible

Routine

MEDIUM 5.5WATCHLISTDOWNGRADEUPGRADEDOWNGRADE

CVE-2021-20191 is a medium-severity flaw (CVSS 5.5) affecting virtualization, ansible, ansible tower. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A flaw was found in ansible. Credentials, such as secrets, are being disclosed in console log by default and not protected by no_log feature when using those modules. An attacker can take advantage of this information to steal those credentials. The highest threat from this vulnerability is to data confidentiality. Versions before ansible 2.9.18 are affected.

Why this priority

On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 71%)
CISA exploited list	No
Weakness	CWE-532
Published	2021-05-26
Last modified	2026-06-17

Publisher (CNA): Red Hat, Inc. · Vendor: oracle · redhat

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-05-26 21:15 UTCPublished CVE record published
2026-06-17 03:33 UTCUpdated Record last modified

oracle virtualization DOWNGRADE

Affected: 4.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 4.0

1. Check installed version

apt-cache policy virtualization || rpm -q virtualization || virtualization --version

2. No fixed release: DOWNGRADE to a release before 4.0 (Debian / Ubuntu)

apt-cache madison virtualization sudo apt install virtualization=<VERSION_BEFORE_4.0> sudo apt-mark hold virtualization

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list virtualization sudo dnf downgrade virtualization-<VERSION_BEFORE_4.0> sudo dnf versionlock add virtualization

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

redhat ansible UPGRADE

Affected: < 2.8.19 · >= 2.9.0 and < 2.9.18 · >= 2.10.0 and < 2.10.7

Fixed in: 2.8.19, 2.9.18, 2.10.7

Safe to downgrade to: a release before 2.9.0

1. Check installed version

apt-cache policy ansible || rpm -q ansible || ansible --version

2. UPGRADE to 2.8.19 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade ansible

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade ansible

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.9.0 (Debian / Ubuntu)

apt-cache madison ansible sudo apt install ansible=<VERSION_BEFORE_2.9.0> sudo apt-mark hold ansible

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list ansible sudo dnf downgrade ansible-<VERSION_BEFORE_2.9.0> sudo dnf versionlock add ansible

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

redhat ansible tower DOWNGRADE

Affected: 3.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.0

1. Check installed version

apt-cache policy ansible-tower || rpm -q ansible-tower || ansible-tower --version

2. No fixed release: DOWNGRADE to a release before 3.0 (Debian / Ubuntu)

apt-cache madison ansible-tower sudo apt install ansible-tower=<VERSION_BEFORE_3.0> sudo apt-mark hold ansible-tower

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list ansible-tower sudo dnf downgrade ansible-tower-<VERSION_BEFORE_3.0> sudo dnf versionlock add ansible-tower

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

redhat cisco nx-os collection UPGRADE

Affected: < 1.4.0

Fixed in: 1.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy cisco-nx-os-collection || rpm -q cisco-nx-os-collection || cisco-nx-os-collection --version

2. UPGRADE to 1.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade cisco-nx-os-collection

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade cisco-nx-os-collection

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

redhat community general collection UPGRADE

Affected: < 1.3.6 · >= 2.0.0 and < 2.0.1

Fixed in: 1.3.6, 2.0.1

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy community-general-collection || rpm -q community-general-collection || community-general-collection --version

2. UPGRADE to 1.3.6 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade community-general-collection

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade community-general-collection

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)

apt-cache madison community-general-collection sudo apt install community-general-collection=<VERSION_BEFORE_2.0.0> sudo apt-mark hold community-general-collection

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list community-general-collection sudo dnf downgrade community-general-collection-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add community-general-collection

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

redhat community network collection UPGRADE

Affected: < 1.3.2 · >= 2.0.0 and < 2.0.1

Fixed in: 1.3.2, 2.0.1

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy community-network-collection || rpm -q community-network-collection || community-network-collection --version

2. UPGRADE to 1.3.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade community-network-collection

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade community-network-collection

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)

apt-cache madison community-network-collection sudo apt install community-network-collection=<VERSION_BEFORE_2.0.0> sudo apt-mark hold community-network-collection

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list community-network-collection sudo dnf downgrade community-network-collection-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add community-network-collection

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2021-20191?

virtualization: downgrade or apply the listed mitigation; ansible: upgrade to 2.8.19, 2.9.18, 2.10.7; ansible tower: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2021-20191 being exploited?

CVE-2021-20191 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2021-20191 affect?

CVE-2021-20191 affects virtualization, ansible, ansible tower. Severity is medium (CVSS 5.5). A flaw was found in ansible. Credentials, such as secrets, are being disclosed in console log by default and not protected by no_log feature when using those modules. An attacker can take advantage of this information to steal those credent

How urgent is CVE-2021-20191?

Priority 31/100. On your watchlist

Software pages

Ansible vulnerabilities · Cisco vulnerabilities

Related CVEs

CVE-2022-2078 MEDIUM 5.5 UPGRADE DOWNGRADE A vulnerability was found in the Linux kernel's nft_set_desc_concat_parse() function .This flaw allows an atta
CVE-2022-27666 HIGH 7.8 UPGRADE MITIGATE A heap buffer overflow flaw was found in IPsec ESP transformation code in net/ipv4/esp4.c and net/ipv6/esp6.c
CVE-2023-5366 HIGH 7.1 UPGRADE DOWNGRADE A flaw was found in Open vSwitch that allows ICMPv6 Neighbor Advertisement packets between virtual machines to
CVE-2023-1668 HIGH 8.2 UPGRADE MITIGATE A flaw was found in openvswitch (OVS)
CVE-2022-2805 MEDIUM 6.5 DOWNGRADE A flaw was found in ovirt-engine, which leads to the logging of plaintext passwords in the log file when using

References

← Back to latest CVEs