CVE-2020-25636: A flaw was found in Ansible Base when using the aws_ssm connection plugin as there is no namespace separation

Routine

MEDIUM 6.6WATCHLISTDOWNGRADE

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

A flaw was found in Ansible Base when using the aws_ssm connection plugin as there is no namespace separation for file transfers. Files are written directly to the root bucket, making possible to have collisions when running multiple ansible processes. This issue affects mainly the service availability.

Why this priority

On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	6.6 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-377, CWE-552
Published	2020-10-05
Last modified	2026-06-17

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

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

Am I affected?

Timeline

2020-10-05 13:15 UTCPublished CVE record published
2026-06-17 03:07 UTCUpdated Record last modified

redhat ansible DOWNGRADE

Affected: 2.10.1 rc2

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.10.1

1. Check installed version

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

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

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

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

dnf --showduplicates list ansible sudo dnf downgrade ansible-<VERSION_BEFORE_2.10.1> 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.

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-2020-25636?

ansible: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-25636 being exploited?

CVE-2020-25636 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-2020-25636 affect?

CVE-2020-25636 affects ansible. Severity is medium (CVSS 6.6). A flaw was found in Ansible Base when using the aws_ssm connection plugin as there is no namespace separation for file transfers. Files are written directly to the root bucket, making possible to have collisions when running multiple ansibl

How urgent is CVE-2020-25636?

Priority 34/100. On your watchlist

Software pages

Ansible vulnerabilities · AWS vulnerabilities

Related CVEs

CVE-2024-0690 MEDIUM 5.0 UPGRADE MITIGATE An information disclosure flaw was found in ansible-core due to a failure to respect the ANSIBLE_NO_LOG config
CVE-2023-5764 HIGH 7.1 UPGRADE DOWNGRADE A template injection flaw was found in Ansible where a user's controller internal templating operations may re
CVE-2023-32983 MEDIUM 5.3 UPGRADE Jenkins Ansible Plugin 204.v8191fd551eb_f and earlier does not mask extra variables displayed on the configura
CVE-2023-32982 MEDIUM 4.3 UPGRADE Jenkins Ansible Plugin 204.v8191fd551eb_f and earlier stores extra variables unencrypted in job config.xml fil
CVE-2022-3697 HIGH 7.5 UPGRADE UPGRADE A flaw was found in Ansible in the amazon.aws collection when using the tower_callback parameter from the amaz

References

← Back to latest CVEs