critical9.3
CVE-2026-133949
pip prior to v26.2.2 the certifi bundled with pip contains the compromised eMudhra certificates.
Impact
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.
An attacker can exploit this over the network, without logging in, without any action by a user. If it succeeds: high risk of data being read, high risk of data or systems being changed.
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| pip | certifi | >= 2019.03.09, < 2026.10.18 | 2026.10.18 |
Affected products
| Vendor | Product | Affected versions |
|---|---|---|
| Pip maintainers | Pip | before 26.2.2 |
| Python Packaging Authority | Pip | before 26.2.2 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/advisories/GHSA-6q48-6c7w-9gw2
- https://github.com/certifi/python-certifi/security/advisories/GHSA-6q48-6c7w-9gw2
- https://discuss.python.org/t/information-for-python-users-regarding-emudhra-emsign-ca-certificate-security-incident/109576
- https://emudhra.we-have-a-problem.com
- https://github.com/advisories/ghsa-6q48-6c7w-9gw2
- https://github.com/pypa/pip/pull/14371
- https://mail.python.org/archives/list/security-announce@python.org/thread/4234WU4ONSVWPT3BIGG6TOJO2UFE26Y6/
- https://www.cve.org/CVERecord?id=CVE-2026-115557
- https://github.com/advisories/GHSA-jg88-vh4g-v698
- https://nvd.nist.gov/vuln/detail/CVE-2026-133949
- https://mail.python.org/archives/list/security-announce@python.org/thread/4234WU4ONSVWPT3BIGG6TOJO2UFE26Y6