CVE-2026-113716
Virtualenv 20.0.0 – 21.14.9
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:LCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-113716 is a medium-severity Link Following (CWE-59) vulnerability in Virtualenv. Its CVSS base score is 4.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Stealth (T1211); ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-105297
Vulnerability Data
virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.9, the builtin creator calls ensure_dir() for executable, library, and package directories, and ensure_dir() accepts an existing symlink to a directory because exists() follows it. Interpreter creation, seed…
more
installation, and activation generation then write through the linked parent outside the requested destination when another local account prepared the tree and the invoking user can access the target. The --clear option removes the planted tree first, while ordinary creation reaches it; arbitrary attacker-selected output bytes are not established. This issue is fixed in version 21.14.9.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Proper enforcement of access authorizations on the resolved target resource stops a link from reaching an unintended object.
Least-privilege limits the damage an attacker can cause after following an unintended link.
Validating file-name inputs can reject or canonicalize names that resolve to links before access occurs.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly require code to validate paths and avoid unsafe link following.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing can detect link-following flaws before release.
Training developers about secure file handling practices (checking for symlinks, using safe file APIs, avoiding predictable temp filenames) reduces some instances of link-following defects, but the effect is a minority one because the practice is fallible and the stronger control is A.8.29 security testing, consistent with the A.8.28 -> CWE-79 and A.6.3 -> CWE-598 anchors.
Secure coding standards directly address canonicalization and symlink attacks during implementation.
A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-59 is an ordinary implementation defect, but the clause's reach is bounded by the supplier's fallible practice and the ceiling on this verb is `partial`.
A.8.8's reach is DISCLOSURE — it surfaces link-following flaws only where they appear as published advisories in third-party components in the inventory. CWE-59 does surface as CVEs (many observed examples), so the disclosed share is non-trivial, but most link-following instances live in first-party code or in third-party components without a published advisory, which A.8.8 does not reach.