How severe is CVE-2026-102930?

No CVSS score has been assigned to CVE-2026-102930 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-102930?

CVE-2026-102930 affects the following packages: virtualenv (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-102930?

Update virtualenv to 21.7.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-102930 is resolved across your whole dependency graph.

How do I detect CVE-2026-102930 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for virtualenv, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-102930 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-102930 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-102930 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-102930?

CVE-2026-102930 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 5th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-102930?

CVE-2026-102930 is classified as CWE-494 (CWE-494). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-102930 published, and has it been updated?

CVE-2026-102930 was published on September 29, 2026 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2026-102930 — virtualenv

Fix: pypa/virtualenv@a01ed3e

CVE-2026-102930 is a CWE-494 vulnerability in virtualenv. A fix is available for virtualenv — see the affected versions and patch details below.

virtualenv: Downloaded seed wheels (pip/setuptools) are not integrity-checked before use

Also known asBIT-virtualenv-2026-102930GHSA-94p9-xgh2-xp45PYSEC-2026-4011

Published

Sep 29, 2026

Updated

Oct 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-102930.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs5th percentile — riskier than 5% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍virtualenv

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

download_wheel() runs pip download and hands the result straight to the seeder, with nothing checking the bytes it gets back. The embedded pip and setuptools wheels carry a BUNDLE_SHA256 that virtualenv checks on every load, but a wheel fetched over the network for the periodic-update feature or the --download flag had no equivalent verification.

A compromised index, a stale mirror, or a MITM'd download (when TLS is intercepted, e.g. via a misconfigured or malicious CA) could substitute a different wheel under the same distribution/version/filename, and virtualenv would cache and seed it into every environment created afterward with no warning.

Fixed by computing the downloaded wheel's sha256 and comparing it against the digest PyPI's public JSON API reports for that exact release, independent of which index actually served the file. The check is skipped, not treated as failure, when a custom index (PIP_INDEX_URL, PIP_EXTRA_INDEX_URL, PIP_INDEX) is configured, since a private index can legitimately serve a different, intentionally rebuilt wheel. Fix: https://github.com/pypa/virtualenv/pull/3251

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`virtualenv`	all versions	21.7.12`pip install --upgrade 'virtualenv==21.7.12'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for virtualenv, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update virtualenv to 21.7.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-102930 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

An Important severity flaw was found in virtualenv, a tool for creating isolated Python virtual environments that is shipped in Red Hat products and offerings including Red Hat Enterprise Linux, Red Hat Ansible Automation Platform, Red Hat AI offerings, and other Red Hat cloud services. When virtualenv fetches pip or…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for CVE-2026-102930 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Ansible Automation Platform 2.6	`ansible-automation-platform-26/eda-controller-rhel9:1791945282`	RHSA-2026:87120
Red Hat Ansible Automation Platform 2.7	`ansible-automation-platform-27/eda-controller-rhel9:1792141010`	RHSA-2026:87124
Red Hat OpenShift AI 2.25	`rhoai/odh-feature-server-rhel9:1792148523`	RHSA-2026:87410
Red Hat OpenShift AI 3.4	`rhoai/odh-feature-server-rhel9:1791863220`	RHSA-2026:84734
Red Hat OpenShift AI 3.5	`rhoai/odh-ta-lmes-job-rhel9:1792501995`	RHSA-2026:86891

Frequently Asked Questions

`download_wheel()` runs `pip download` and hands the result straight to the seeder, with nothing checking the bytes it gets back. The embedded pip and setuptools wheels carry a `BUNDLE_SHA256` that virtualenv checks on every load, but a wheel fetched over the network for the periodic-update feature or the `--download` flag had no equivalent verification. A compromised index, a stale mirror, or a MITM'd download (when TLS is intercepted, e.g. via a misconfigured or malicious CA) could substitute a different wheel under the same distribution/version/filename, and virtualenv would cache and seed

O3 Security · Impact-Aware SCA

Is CVE-2026-102930 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works