CVE-2020-25635
Ansible does not collect garbage after playbook run
Reported by redhat · Published October 5, 2020
ansible is fixed in 2.10.1 (PyPI)
A flaw was found in Ansible Base when using the aws_ssm connection plugin as garbage collector is not happening after playbook run is completed. Files would remain in the bucket exposing the data. This issue affects directly data confidentiality.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| ansible | PyPI | 2.10.1 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| AWS Community | Community Collections | from 1.0.0 to 1.2.0 |
| AWS Community | Community Collections | 1.0.0 |
| PyPI | ansible | 0 |
Timeline
- Oct 5, 2020 CVE Published
- Apr 14, 2021 EPSS Score (30 in total, the first dated here)
- Oct 31, 2025 CVE Updated
- Mar 9, 2026 Security Advisory
- Sep 2, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2020-25635
vulnetix vdb fixes CVE-2020-25635
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2020-25635/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- x_refsource_MISC
- x_refsource_CONFIRM
- https://nvd.nist.gov/vuln/detail/CVE-2020-25635 advisory
- https://github.com/advisories/GHSA-f556-49jc-4rvc advisory
- https://github.com/ansible-collections/community.aws/pull/237#issuecomment-1468591094 patch
- https://github.com/ansible/ansible url
- https://github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2020-220.yaml advisory