Skip to main content
VulnerabilityPublished

CVE-2026-113714: virtualenv · Downloaded wheel selection and caching precede verification

Affects toxSource GCVE Database

0
Authoritative record:CVE-2026-113714· Low 2.3

Not known to be exploited · CVSS 2.3 Low : upgrade to 4.67.0 when convenient.

Data as of 27 Oct 2026, 06:44 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.67.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

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 tox to 4.67.0.

Affected software

ProductAffectedFixed in
Homebrewtoxpkg:brew/toxOther threatsAffected
  • >=4.62.0 <4.67.0
Fixed in
  • 4.67.0

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 4.67.0 or later, where the vulnerability is fixed by downloading wheels to a temporary location and verifying them before caching. Users relying on default PyPI indexes and without custom index configurations are not affected. No additional mitigation is required once patched.

Description

A vulnerability in virtualenv versions >=4.62.0 <4.67.0 allows a downloaded wheel file to be cached and reused before its integrity verification completes. This occurs because virtualenv writes the downloaded wheel directly into the reusable wheel cache and then verifies the wheel by parsing pip's textual output rather than verifying the actual cached file. If verification fails, the corrupted or modified wheel remains in the cache and can be reused later, potentially leading to execution of tampered code. The issue was fixed in version 4.67.0.

References

Community reviews

Loading reviews…