VDB

CVE-2020-25635

CVE-2020-25635 PUBLISHED CVSS 5 MEDIUM

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.

PackageEcosystemFixed in
ansiblePyPI2.10.1

Risk scores

CVSS 3.1
5
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Affected products

VendorProductVersions
AWS CommunityCommunity Collectionsfrom 1.0.0 to 1.2.0
AWS CommunityCommunity Collections1.0.0
PyPIansible0

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

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›