CVE-2026-133949 in the critical feed json
pip bundles compromised eMudhra certificates via certifi
published 6h ago modified 5h ago also EUVD-2026-131829
- cvss
- 9.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2026-133949 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 6h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N |
Inferred packages
No advisory lists a package for this vulnerability yet. The CVE names these as products and links their GitHub repository, and the package registry names the same repository, so they are probably the affected packages. Low confidence: the versions are the CVE’s own for the product, and a stack check reports the package as unchecked when there are none.
| ecosystem | package | repository | affected |
|---|---|---|---|
| pypi | pip | pypa/pip | < 26.2.2 |
Affected products
- Pip maintainers pip
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
- Technology feeds
References
-
github.com
/pypa/pip/pull/14371
patch
-
mail.python.org
/archives/list/security-announce@python.org/thread/4234WU4ONSVWPT3BIGG6TOJO2UFE26Y6/
vendor-advisory
-
github.com
/advisories/ghsa-6q48-6c7w-9gw2
related
-
discuss.python.org
/t/information-for-python-users-regarding-emudhra-emsign-ca-certificate-security-incident/109576
related
-
cve.org
/CVERecord?id=CVE-2026-115557
related
Sources
- CVE List CVE-2026-133949
- NVD CVE-2026-133949
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.