Skip to main content
VulnerabilityPublished

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

Affects poetrySource GCVE Database

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

Not known to be exploited · CVSS 4.5 Medium : upgrade to 2.5.1_1 or 1.2.2_1 when convenient.

Data as of 27 Oct 2026, 06:45 UTC

CVSS 3.1 base score
4.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.5.1_1, 1.2.2_1
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. Weaponised: 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 26 Oct 2026.

What to do

Upgrade poetry to 2.5.1_1 or 1.2.2_1.

Affected software

ProductAffectedFixed in
Homebrewpoetrypkg:brew/poetryOther threatsAffected
  • >=1.1.11 <1.2.2_1
  • >=1.8.0 <2.5.1_1
Fixed in
  • 1.2.2_1
  • 2.5.1_1

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

AI-suggested

A patch is available in virtualenv versions 1.2.2_1 and 2.5.1_1 that adds checks to ensure deletion paths are contained within the environment root, preventing arbitrary file deletion. Users should upgrade to these fixed versions to remediate the vulnerability. Avoid reusing environments with untrusted or attacker-controlled distribution metadata. Using the '--clear' option removes existing metadata before environment creation and can mitigate the issue.

Description

A vulnerability in virtualenv's app-data seeder allows deletion of files outside the intended environment during seed package reinstallation. This occurs because the uninstall process joins paths from distribution metadata without verifying containment within the environment, enabling deletion of arbitrary user files if malicious metadata is present. The issue requires an environment reused with attacker-controlled metadata and deletion rights by the invoking user. A fix is available in versions 1.2.2_1 and 2.5.1_1.

References

Community reviews

Loading reviews…