CVE-2020-25635: Ansible does not collect garbage after playbook run
A flaw was found in Ansible Base when using the awsssm connection plugin as its garbage collector is not happening after the playbook run is completed. Files would remain in the bucket exposing the data. This issue directly affects data confidentiality.
Published Oct 31, 2025
Affected packages
ansible
- Ecosystem
- PyPI
- Affected
- < 2.10.1
- Fixed in
- 2.10.1
- Check
pip show ansible
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
A flaw was found in Ansible Base when using the aws_ssm connection plugin as its garbage collector is not happening after the playbook run is completed. Files would remain in the bucket exposing the data. This issue directly affects data confidentiality.
References
- https://nvd.nist.gov/vuln/detail/CVE-2020-25635
- https://github.com/ansible-collections/community.aws/issues/222
- https://github.com/ansible-collections/community.aws/pull/237#issuecomment-1468591094
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-25635
- https://github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2020-220.yaml
- https://github.com/advisories/GHSA-f556-49jc-4rvc
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
