Python Packaging Authority pip compromised certificates trusted via bundled certifi file
pip versions before 26.2.2 bundle a certifi CA store containing compromised eMudhra certificates. Fixed in pip 26.2.2.
- Exploited
- No known exploitation
- Fix
- Fixed in 26.2.2
- Who is exposed
- Not reported
Summary
The pip package installer from Python Packaging Authority bundles a certifi certificate file that contains compromised eMudhra certificates, which an attacker could abuse to be trusted. The flaw can be reached remotely, without logging in or any user action, in pip releases before the fixed version.
Written by a model
Original description
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. See the references below for more information.
Who should check
Teams running pip before 26.2.2 in Python environments, virtualenvs, or container images, including Python.org macOS installs that ship certifi
“pip prior to v26.2.2 the certifi bundled with pip contains the compromised”
What to do
Upgrade to a fixed version: 26.2.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133949 (pip bundles compromised eMudhra certificates via certifi), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133949 (entry last updated 2026-11-20):
Affected:
- PyPI package pip: fixed in 26.2.2
Fixed versions: 26.2.2.
Conditions (all must be true for the bug to be hit):
- pip versions before v26.2.2, which bundle a certifi CA store with the compromised eMudhra certificates (source: https://mail.python.org/archives/list/security-announce@python.org/thread/4234WU4ONSVWPT3BIGG6TOJO2UFE26Y6/)
- Certifi versions before 2026.10.18, which include the emSign root CA in their bundled CA store (source: https://github.com/advisories/ghsa-6q48-6c7w-9gw2)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-133949 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133949 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://mail.python.org/archives/list/security-announce@python.org/thread/4234WU4ONSVWPT3BIGG6TOJO2UFE26Y6/
- https://github.com/pypa/pip/pull/14371
- https://github.com/advisories/ghsa-6q48-6c7w-9gw2
- https://discuss.python.org/t/information-for-python-users-regarding-emudhra-emsign-ca-certificate-security-incident/109576
- https://www.cve.org/CVERecord?id=CVE-2026-115557
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133949
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133949"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach20/20pip: 149.9M downloads a week
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 95 if added to CISA KEV
- Would score about 90 if CISA's SSVC rates exploitation active
- Would score about 55 if advisories confirm default setups are exposed
Impact
- Widely usedpip has 149.9m weekly downloads. pypistats.org4.9k packages depend on pip. deps.dev
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
- Posted on X by cve.now
Evidence 7
| Kind | Source |
|---|---|
| CVE record 3Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133949 |
| Record | NVD · CVE-2026-133949 |
| Link | cve.org · CVERecord?id=CVE-2026-115557 |
| Other links 4 | |
| Advisory | GitHub Advisory Database · Advisory ghsa-6q48-6c7w-9gw2 |
| Advisory | mail.python.org · archives/list/security-announce@python.org/thread/4234WU4ONSVWPT3BIGG6TOJO2UFE26Y6 |
| Patch | GitHub · pypa/pip · Pull request #14371 |
| Link | discuss.python.org · t/information-for-python-users-regarding-emudhra-emsign-ca-certificate-security-incident/109576 |
Questions about CVE-2026-133949
Is CVE-2026-133949 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The CA store that pip bundles through certifi includes eMudhra certificates that are compromised. An attacker holding one of the compromised eMudhra intermediate keys could issue valid-looking certificates for any hostname and, if on-path, intercept or modify TLS traffic from clients that trust the certifi bundle.
Source: mail.python.org, github.com
Which versions are affected by CVE-2026-133949?
pip (PyPI): before 26.2.2.
Source: cve.now feed data
Am I affected, and how do I check?
pip versions before 26.2.2 bundle a certifi CA store with the compromised eMudhra certificates. Certifi versions before 2026.10.18 include the emSign ECC Root CA - G3 root certificate in their bundled CA store. To check, run pip --version for the pip version and pip show certifi for the certifi version.
Source: mail.python.org, github.com
How do I fix CVE-2026-133949?
Upgrade pip to 26.2.2 or later, which is the fixed version listed for this vulnerability.
Source: mail.python.org, github.com
Related
- CVE-2019-20916The pip package before 19.2 for Python allows Directory Traversal when a URL is given in an install command, because a Content-Disposition…
- CVE-2025-8869Fallback tar extraction in pip doesn't check symbolic links point to extraction directory
- CVE-2013-5123The mirroring support (-M, --use-mirrors) in Python Pip before 1.5 uses insecure DNS querying and authenticity checks which allows…
- CVE-2021-3572A flaw was found in python-pip in the way it handled Unicode separators in git references.
- CVE-2026-13346pip absolute path traversal during download from malicious package indexes
- CVE-2023-5752Mercurial configuration injectable in repo revision when installing via pip
No corrections so far. Something wrong on this page? Report an error.