Vulnerability in virtualenv (CVE-2026-102930)
Summary
Vulnerability in virtualenv (CVE-2026-102930). Risk of unauthorized operations or information disclosure. Exploitable via BUNDLE_SHA256. Mitigation: upgrade to 21.7.12 or later.
Original description
The description as published by the source.
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 in 21.7.12 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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-102930 has been found in virtualenv.
Attackers can target a specific entry point like BUNDLE_SHA256 over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade virtualenv to 21.7.12 or later.
If unsure, ask your IT team or search "virtualenv CVE-2026-102930" on the vendor's site.
CVE-2026-102930 (virtualenv) — CWE-494
Attack surface: BUNDLE_SHA256 / PIP_INDEX_URL / PIP_EXTRA_INDEX_URL / PIP_INDEX
Patched: 21.7.12 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-494) exists in virtualenv. Attackers reach the vulnerable code path via BUNDLE_SHA256.
Check the vendor advisory for the affected versions of virtualenv. Attack surface: BUNDLE_SHA256 / PIP_INDEX_URL / PIP_EXTRA_INDEX_URL / PIP_INDEX.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 21.7.12.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'virtualenv' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'virtualenv' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
virtualenvを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade virtualenv to 21.7.12ステージング環境で 21.7.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-102930 python-virtualenv
References
- advisory nvd.nist.gov
- package github.com
- package pypi.org
- patch github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com