Python ecosystem patches eMudhra CA compromise across pip, certifi, PyPI, and core language

On October 20, 2026, the eMudhra Intermediate Certificate Authority compromise forced a rapid, ecosystem-wide response from the Python community to protect the integrity of package installation and HTTPS communications. Seth Larson, the PSF's Alpha-Omega-funded Security Developer-in-Residence, led coordination that delivered patches across Python, pip, certifi, uv, sigstore, virtualenv, conda, pixi, manylinux, and PyPI publishing tools within 48 hours. The incident exposed a critical dependency chain: Python bundles pip via ensurepip, pip bundles Requests which depends on certifi, and certifi repackages Mozilla's CA bundle—making all three components essential to bootstrap secure package installation.

Because certifi only ships root CAs and not intermediates, the remediation required removing the compromised root certificate "emSign Root TLS CA - G3" entirely. For older Python versions that cannot upgrade pip due to compatibility constraints, the PSF backported a "last-resort" TLS denylist via CVE-2026-115557 to reject the compromised intermediates during handshake. The response also highlighted a structural gap: browsers could revoke certificates dynamically via Certificate Revocation Lists without software updates, while Python packaging tools could not, prompting future evaluation of CRL integration and the upki project already adopted by Ubuntu.

Certificate chain architecture and remediation mechanics

• Critical dependency chain: Python's ensurepip mechanism bundles pip into new virtual environments; pip bundles Requests, which depends on certifi; certifi repackages Mozilla's root CA bundle without intermediates, creating a single path for trust establishment that all required coordinated patching.
• Root CA removal strategy: Because certifi cannot distrust individual intermediate certificates directly, the remediation removed the root CA "emSign Root TLS CA - G3" from the bundle, cascading distrust to all impacted intermediate certificates issued under that root.
• Legacy Python backport: Python added a "last-resort" denylist in the TLS handshake implementation to reject compromised intermediate certificates, tracked as CVE-2026-115557 and backported to older Python versions that cannot upgrade their bundled pip versions.
• Infrastructure scope: Patches were applied across PyPI, python.org, Python release build bots, and container images, with vulnerable versions of certifi, pip, and sigstore remediated across all PSF-stewarded services.
• CRL capability gap: The incident revealed that browsers secured connections through Certificate Revocation Lists without requiring software updates, while Python tools like pip, git, and uv lacked equivalent runtime revocation checking, prompting future integration of technologies like the upki project.

Why it matters

This incident demonstrates how dedicated security funding—specifically Alpha-Omega's support for the PSF Security Developer-in-Residence—translates into measurable supply chain protection for one of the world's most widely used programming ecosystems. The coordinated response across volunteer-maintained projects, combined with proactive maintainer outreach and clear advisory publishing, sets a template for how language foundations can operationalize security response at scale. For Linux distributions and system administrators, the backported denylist and certifi patches reduce exposure from embedded or legacy Python installations, while the identified CRL gap suggests future hardening that could benefit all TLS-dependent open-source tooling beyond Python alone.