cve.bz

CVE-2026-133949 pip bundles compromised eMudhra certificates via certifi

9.3 criticalEPSS 0.5%

Critical (9.3) in pip maintainers pip. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

9.3 critical
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
EPSS
0.5% estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-11-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
Assigned by
PSF (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-133949 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-133949?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-133949?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-133949 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Pip maintainers pipbefore 26.2.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Alpinev3.23py3-pip25.1.1-r2ALPINE-CVE-2026-133949
Alpinev3.24py3-pip26.1.2-r1ALPINE-CVE-2026-133949
Azure Linux3python-pipno fix listedAZL-115916

From the distributions' data via OSV.dev: the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Alpine.

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON