pip: Vendored certifi trusts compromised eMudhra intermediates, enabling TLS interception (CVE-2026-133949)
Severity: critical · Patch status: patched · Since 2026-10-18 · CVE-2026-133949
In October 2026 eMudhra disclosed that the private keys of eight of its intermediate CAs were recoverable from their public certificates, because the keys were generated incorrectly. Those intermediates chain to emSign ECC Root CA - G3, which the certifi CA bundle trusts. pip always loads trust anchors from its vendored certifi, so every pip release before 26.2.2 keeps trusting certificates issued under those intermediates, even when the operating system trust store has been fixed. An on-path attacker holding one of the keys could impersonate HTTPS endpoints that pip contacts, such as package indexes, and tamper with downloads. pip 26.2.2 vendors certifi 2026.10.19, which drops emSign ECC Root CA - G3; pip 26.3 vendors 2026.10.23. Where pip cannot be upgraded first, Python 3.11.18, 3.12.16, 3.13.18, 3.14.10 and 3.15.2 or later reject the compromised intermediates inside the ssl module (CVE-2026-115557). The CVE was published on 2026-11-20 by Python's CNA, but the first public fix and advisory date from 2026-10-18 to 2026-10-20. No in-the-wild exploitation has been confirmed. The researchers do not know whether attackers used the flawed keys against clients that do not enforce Certificate Transparency, and the original reporter's page includes a working interception demonstration against git.
What to do
- Upgrade pip to 26.2.2 or later on all developer workstations, build agents, and CI/CD runners; prioritize systems that fetch packages from the internet.
- If direct pip upgrade is blocked, first upgrade Python to 3.15.2, 3.14.10, 3.13.18, 3.12.16, 3.11.18 or later (these reject the compromised intermediates, CVE-2026-115557), then upgrade pip.
- Upgrade certifi to 2026.10.19 or later wherever it is vendored or pinned (for example in application environments and container images), and rebuild container images with layer caching disabled so the old bundle is not reused.
- On python.org macOS installs, upgrade pip and certifi in that interpreter; the installer ships its own certifi bundle.
- Use hash-pinned requirements and a known-secure pip bootstrap where upgrades cannot be completed immediately.
- Audit recent package-install traffic for unexpected TLS endpoints or certificate anomalies; treat credentials/tokens used by affected pip as potentially exposed if compromise is suspected.
Fixed versions
- pip 26.2.2
- pip 26.3
- certifi 2026.10.19
Sources
All live incidents on Threat Watch