What is CVE-2026-102930?

CVE-2026-102930 is virtualenv: Downloaded seed wheels (pip/setuptools) are not integrity-checked before use. The supplied enrichment data classifies it as Unclassified mapped to CWE-494 CWE-494.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-102930. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-102930 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2026-102930. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-102930 using CVSS 7.7, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

high

CVE-2026-102930

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

virtualenv is a tool for creating isolated virtual python environments. Prior to 21.7.12, download_wheel() accepts pip and setuptools seed wheels fetched for periodic updates or the --download option without checking their bytes against an authoritative digest equivalent to the embedded wheels' BUNDLE_SHA256 verification. A compromised index, stale mirror, or intercepted TLS connection can substitute a different wheel under the requested distribution, version, and filename, after which virtualenv caches and seeds the attacker-controlled wheel into subsequently created environments. The verification applies to the default PyPI path and is intentionally skipped when PIP_INDEX_URL, PIP_EXTRA_INDEX_URL, or PIP_INDEX configures a custom index that may legitimately publish rebuilt wheels. This issue is fixed in version 21.7.12.

Published Sep 29, 2026Updated Sep 29, 2026Sources: NVD, pypa (CNA), GitHub, Red Hat (VEX)

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

Not scored

FIRST has not published a score

Affects

pypa

virtualenv

CVSS base

7.7

high · 2 sources

Remediation

The vendor's own words where we have them.

Upgrade virtualenv to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

Red Hat VEX · CVE-2026-102930

fixed0affected48not affected0

none_available: Affected

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
pypa	virtualenv	< 21.7.12	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack Complexity

High

Attack Vector

Network

Privileges Req

None

User Interaction

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.7	CVSS 4.0	high	—	—	pypa (CNA)
7.5	CVSS 3.1	high	—	—	Red Hat (VEX)

CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Weakness & attack patterns

CWE-494

Inferred from the weakness class — not observed against this CVE.

T1195.002Supply Chain Compromise: Compromise Software Supply Chain
T1072Software Deployment Tools
T1195.001Supply Chain Compromise: Software Dependencies and Development Tools

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable virtualenv.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.7 (AV:N)
Sep 29, 2026 · NVD
Initial · CVE published
Sep 29, 2026 · NVD

References

7 on the record

github.com/pypa/virtualenv/commit/a01ed3e2f239d6ab1fce62c5c7664ccf268fff6d
Exploit, Third Party Advisory
github.com/pypa/virtualenv/pull/3251
Exploit, Third Party Advisory
github.com/pypa/virtualenv/security/advisories/GHSA-94p9-xgh2-xp45
Exploit, Third Party Advisory
access.redhat.com/security/cve/CVE-2026-102930
Vendor Advisory
bugzilla.redhat.com/show_bug.cgi?id=2543652
Vendor Advisory
www.cve.org/CVERecord?id=CVE-2026-102930
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-102930
NVD

Elsewhere on this site

pypaevery CVE for this vendor
Unclassifiedsame class
CWE-494other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-102930 is virtualenv: Downloaded seed wheels (pip/setuptools) are not integrity-checked before use, a high vulnerability affecting virtualenv from pypa. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-102930. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-102930. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.7 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.