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

> Attackers can inject malicious code into virtual environments by substituting seed wheels when custom indexes are configured, requiring an upgrade to fix.

- **Severity:** High 7.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** AZL-105669, BIT-virtualenv-2026-102930, DEBIAN-CVE-2026-102930, ECHO-2248-faed-ae67, GHSA-94p9-xgh2-xp45, MINI-cpmh-xwwj-c7xf, MINI-jj2g-6j63-g478, PYSEC-2026-4011, ROOT-APP-PYPI-CVE-2026-102930, UBUNTU-CVE-2026-102930

## What is CVE-2026-102930?

CVE-2026-102930 is a high-severity vulnerability in pypa virtualenv, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-494 (Download of Code Without Integrity Check)

## Which versions are affected by CVE-2026-102930?

4 open source packages ship an affected version, including virtualenv.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `virtualenv` | Bitnami | All versions | 21.7.12 |
| `virtualenv` | PyPI | All versions | 21.7.12 |
| `virtualenv` | PyPI | All versions | 21.7.12 |
| `virtualenv` | PyPI | All versions | 21.7.12 |

## How do I fix CVE-2026-102930?

Upgrade virtualenv to 21.7.12 or later.

## Is CVE-2026-102930 being exploited?

There is no known exploitation of CVE-2026-102930 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102930 and fix it if it is affected.

What it is: CVE-2026-102930 is a high-severity vulnerability in pypa virtualenv, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-102930 in the wild and no public exploit code.

Affected packages and fixed versions:
- virtualenv (Bitnami): affected all versions; fixed in 21.7.12
- virtualenv (PyPI): affected all versions; fixed in 21.7.12
- virtualenv (PyPI): affected all versions; fixed in 21.7.12
- virtualenv (PyPI): affected all versions; fixed in 21.7.12

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102930/ (Markdown: https://insights.sbomify.com/CVE-2026-102930/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102930
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102930
- OSV: https://osv.dev/vulnerability/CVE-2026-102930

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102930/
Summaries are generated and may contain mistakes; the official description above is the record.