Skip to main content
VulnerabilityPublished

CVE-2026-113719: virtualenv · Seed replacement does not contain metadata deletion paths

Affects virtualenvSource GCVE Database

0
Compare
Authoritative record:CVE-2026-113719· Medium 4.5

Not known to be exploited · CVSS 4.5 Medium : upgrade to 21.14.9 when convenient.

Data as of 29 Oct 2026, 14:41 UTC

CVSS 3.1 base score
4.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.14.5
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 21.14.9
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade virtualenv to 21.14.9.

Affected software

ProductAffectedFixed in
Bitnamivirtualenvpkg:bitnami/virtualenvOther threatsAffected
  • <21.14.9
Fixed in
  • 21.14.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade virtualenv to version 21.14.9 or later, where this issue is fixed. Avoid reusing existing seed-package metadata during environment creation, or create fresh environments or use the --clear option to bypass the vulnerable cleanup path.

Description

A vulnerability in virtualenv prior to version 21.14.9 allows deletion of files outside the intended environment during environment creation if existing seed-package metadata is reused. This occurs due to improper handling of metadata paths, which can lead to deletion of files outside the environment root with the invoking user's permissions. Fresh environments or those created with --clear are not affected. The issue is fixed in version 21.14.9.

References

Community reviews

Loading reviews…