CVE-2020-10691

An archive traversal flaw was found in all ansible-engine versions 2.9.x prior to 2.9.7, when running ansible-galaxy collection install. When extracting a collection .tar.gz file, the directory is created without sanitizing the filename. An attacker could take advantage to overwrite any file within the system.

Published: 2020-04-30 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-10691 is rated Low Risk (30.7/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.36%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-10691

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.10% 0.36% +0.26%
2 2025-03-19 0.04% 0.10% +0.05%
3 2023-03-07 — 0.04% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-10691

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.2 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.0 2.7 [email protected]
5.2 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.0 2.7 [email protected]
3.6 2.0 LOW
AV:L/AC:L/Au:N/C:N/I:P/A:P Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 3.9 4.9 [email protected]

Weakness enumeration for CVE-2020-10691

GitHub Security Advisory for CVE-2020-10691

OS Trackers for CVE-2020-10691

vendor priority summary link
alpine medium CVE-2020-10691: 2 source package rows (ansible, ansible-base); 4 state rows across 4 repos (3.11-main, 3.12-main, edge-community, edge-main); fixed 4, open 0. https://security.alpinelinux.org/vuln/CVE-2020-10691
debian not yet assigned CVE-2020-10691 not yet assigned priority: Debian including 1 source packages (ansible), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2020-10691
redhat medium — https://access.redhat.com/security/cve/CVE-2020-10691
suse medium CVE-2020-10691 severity moderate: SUSE including 116 source package names (ansible-10-10.6.0-1.1, ansible-11-11.11.0-1.1, …), 247 product×package rows across 9 product lines (HPE Helion OpenStack 8, SUSE Linux Enterprise Server 11 SP3-TERADATA, … (9 product lines)): Fixed 246, Known Not Affected 1. https://www.suse.com/security/cve/CVE-2020-10691/
ubuntu medium CVE-2020-10691 medium priority: Ubuntu including 1 source packages (ansible), 17 status rows across 17 suites (bionic, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 14, ignored 1, needed 1, released 1. https://ubuntu.com/security/CVE-2020-10691

Affected software / configurations for CVE-2020-10691

Vendor Product Version Raw CPE
redhat ansible_engine >= 2.9.0, < 2.9.7 cpe:2.3:a:redhat:ansible_engine:*:*:*:*:*:*:*:*
redhat ansible_tower 3.0 cpe:2.3:a:redhat:ansible_tower:3.0:*:*:*:*:*:*:*

References for CVE-2020-10691

URL Tags
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-10691 Issue Tracking Mitigation Vendor Advisory
https://github.com/ansible/ansible/pull/68596 Patch Third Party Advisory
cvelogic Threat Intelligence