CVE-2026-133949: pip bundles compromised eMudhra certificates via certifi
pip prior to v26.2.2 the certifi bundled with pip contains the compromised eMudhra certificates.
Upgrading to a secure version of pip should be done either by first upgrading Python to a version that rejects the compromised intermediates ( https://www.cve.org/CVERecord?id=CVE-2026-115557 ) or use hash pinning with a known-secure version of pip.
Other sources
pip prior to v26.2.2 the certifi bundled with pip contains the compromised eMudhra certificates.
Upgrading to a secure version of pip should be done either by first upgrading Python to a version that rejects the compromised intermediates (CVE-2026-115557) or use hash pinning with a known-secure version of pip. pip is not vulnerable when using a Python version that rejects the compromised certificates. See the references below for more information.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pipto a version that resolves this vulnerability.Fixed in v26.2.2 - Compensating control
Use hash pinning with a known-secure version of pip.
Event History
Frequently Asked Questions
Which installations are actually vulnerable?
pip versions before 26.2.2 are affected when they use a Python version that does not reject the compromised eMudhra intermediates. pip is not vulnerable when run with a Python version that rejects those certificates.
What should be done if pip cannot be upgraded normally?
First upgrade Python to a version that rejects the compromised intermediates, then upgrade pip. Alternatively, use hash pinning with a known-secure version of pip.
What attacker capability makes this issue relevant?
The affected pip bundle trusts compromised eMudhra certificates through certifi. An attacker would need to use those compromised certificates in the relevant certificate-validation path; the advisory provides no additional exploitation prerequisites.