Skip to content
Fencer Intel
low 2.3

CVE-2026-113714 json

virtualenv: Downloaded wheel selection and caching precede verification

published 20d ago modified 11d ago also BIT-virtualenv-2026-113714 , EUVD-2026-105260 , GHSA-494p-63j8-28p3

cvss
2.3
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 16%
public exploits
0
none known

Summary

virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.9, download_wheel() writes package-index downloads directly into the reusable wheel/house cache before selecting a verification target from pip's textual Saved output. With default-index digest comparison enabled, a controlled package index can inject a misleading Saved line through a discarded link's data-requires-python attribute; this forged-line variant also requires knowledge of an absolute path to the genuine bundled wheel. The wrong path can then be hashed, while a digest mismatch leaves the rejected archive in the cache for later selection without verification. A separate rejected-cache-file variant requires control over downloaded data or archive selection but not the forged-line prerequisites. Explicit custom-index exceptions are outside the promised PyPI comparison, and the issue does not independently bypass TLS or establish control of default PyPI. This issue is fixed in version 21.14.9.

Patch / fix

  • pypi virtualenv 21.14.9
  • bitnami virtualenv 21.14.9
  • virtualenv virtualenv 21.14.9
  • python-virtualenv openSUSE Tumbleweed 21.15.1-1.1

opensuse advisories openSUSE-SU-2026:12372-1

Is CVE-2026-113714 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-113714 updated cvss 5.0

virtualenv: virtualenv: Unverified package installation via premature cache storage

  • Red Hat OpenShift Lightspeed openshift-lightspeed/lightspeed-service-api-rhel9 Red Hat Ansible Automation Platform 2 python-virtualenv 20.25.1-2.el10ap, python3.11-virtualenv 20.25.1-1.el9ap, python3.12-virtualenv 20.25.1-2.el9ap, ansible-automation-platform-26/controller-rhel9, ansible-automation-platform-27/controller-rhel9, ansible-automation-platform-26/eda-controller-rhel9, +2 more Red Hat OpenShift AI (RHOAI) rhoai/odh-ta-lmes-job-rhel9, rhoai/odh-kserve-agent-rhel9, rhoai/odh-kserve-router-rhel9, rhoai/odh-feature-server-rhel9, rhoai/odh-kserve-controller-rhel9, rhai-early-access/docling-serve-cuda-rhel9, +6 more Red Hat OpenShift Container Platform 4 python-virtualenv 20.25.1-2.el10ap Red Hat OpenShift Dev Spaces devspaces/udi-rhel9 Red Hat Satellite 6 satellite/iop-yuptoo-rhel9, satellite/iop-host-inventory-rhel9, satellite/iop-advisor-backend-rhel9
    affected: no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
13d ago

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/pypa/virtualenv/security/advisories/GHSA-494p-63j8-28p3 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 2.3 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
CNA 4.0 2.3 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
pypi virtualenv
<21.14.9
21.14.9
bitnami virtualenv
<21.14.9
21.14.9

Affected products

  • pypa virtualenv

Classification

Weakness
  • CWE-354 Improper Validation of Integrity Check Value

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.