What happened
Many Python programs, including the requests and urllib3 libraries, check secure (HTTPS) connections against a list of trusted certificate authorities from the certifi package. The pip tool, used to install Python packages, carries its own built-in copy of that list. Until now, it included the emSign ECC Root CA G3 root certificate from the eMudhra certificate authority.
According to the GitHub security advisory, eight eMudhra intermediate certificates that chain to this root have compromised private keys, and the authority has revoked them. Python announced the incident on October 20, 2026 on the discuss.python.org forum. In the same thread, Christian Heimes added that the cause was extremely weak private keys on all eight authorities.
The Python security team published a separate vulnerability for pip, CVE-2026-133949, on November 20, 2026. It affects pip versions before 26.2.2. The flaw is not in the CISA KEV catalog, and the European EUVD database (entry EUVD-2026-131829) does not list it as exploited. Neither Python nor GitHub reports active exploitation.
Why it is dangerous
This is an improper certificate validation flaw (CWE-295). A certificate works like a website’s ID card, and a certificate authority is the office that issues it. If someone gets hold of the official stamp, they can produce a fake ID that looks perfectly genuine. According to GitHub, anyone holding one of the leaked keys can issue a valid-looking certificate for any domain.
A fake certificate alone is not enough, though. The attacker also has to be “on-path” between you and the server, for example on the same Wi-Fi network or on a compromised router. In that position, a man-in-the-middle attack lets them intercept or modify encrypted traffic from software that trusts the certifi bundle. GitHub lists the requests and urllib3 libraries, pip and the Python.org macOS installer as examples. No login or user interaction is required.
With pip, altered traffic can include the packages being downloaded, which is code that later runs on your systems. Python warns that attacks could target connections to python.org and pypi.org as well. Christian Heimes points out that pip always loads its built-in certificate list alongside the system trust store, and there is no supported way to turn that off. Distrusting the certificates at the operating system level therefore does not protect pip.
CVSS rates vulnerability severity on a scale from 0 to 10. The Python security team scored this flaw 9.3 under CVSS 4.0, which is critical. GitHub rates the related certifi advisory at 9.1 under CVSS 4.0. Unlike Python, it lists high attack complexity and additional attack requirements. The CISA KEV catalog, a list of flaws with confirmed exploitation, does not include this one. An EPSS score, which estimates the likelihood of exploitation in the next 30 days, is not yet available.
Who is affected
This affects anyone who uses Python and installs packages. Typical environments include developer workstations, servers running Python applications, CI/CD build pipelines, Docker images and data analysis setups.
pipversions before 26.2.2certififrom version 2019.03.09 up to (but not including) 2026.10.18, and applications that use it, for example viarequestsorurllib3- Python from the official python.org macOS installer, which ships a certifi certificate list
- new virtual environments created with an older Python, which automatically get the older bundled pip
- container images with old certifi or pip
According to the description in the CVE record, pip is not vulnerable when running on a Python version that rejects the compromised certificates by itself. Python’s announcement names these versions as 3.15.2, 3.14.10, 3.13.18, 3.12.16 and 3.11.18. Python says uv, Hatch, pyenv and the official Docker Python images did not bundle these root certificates, but upgrading is still recommended. Python 3.10 and older no longer receive security fixes.
How to check if you are affected
The following commands only print version information and change nothing. Run them everywhere you use Python, including virtual environments and containers.
python3 --version
python3 -m pip --version
Version of the standalone certifi package (versions before 2026.10.18 are affected, 2026.10.19 or later is recommended). This command does not show the copy of certifi built into pip, which depends on the pip version.
python3 -m pip show certifi
Find virtual environments on a server by looking for pyvenv.cfg files. This command lists them together with the pip version in each one:
find / -path /proc -prune -o -name pyvenv.cfg -print 2>/dev/null | while IFS= read -r f; do d=$(dirname "$f"); [ -x "$d/bin/python" ] && echo "$d: $("$d/bin/python" -I -m pip --version 2>/dev/null)"; done
If you use uv, conda or other tools, check their version (for example uv --version) and compare it with the list in the fix section. Also review certifi versions pinned in requirements.txt or lock files.
How to fix it
The fixed versions are pip 26.2.2 and certifi 2026.10.18. Python and GitHub both recommend certifi 2026.10.19, which restores the unaffected emSign root certificates. Python has also released 3.15.2, 3.14.10, 3.13.18, 3.12.16 and 3.11.18, which reject the compromised intermediate certificates automatically. Updating through a vulnerable pip itself goes over the network, so follow this order:
- First, update Python to a fixed version using your distribution’s package manager or the official installer. After that, updating pip is safe.
- If you cannot update Python right away, install pip 26.2.2 with SHA256 hash pinning. Verify the checksum on pypi.org in a web browser, which already has updated certificates.
- In every virtual environment, update pip to 26.2.2 or later and certifi to 2026.10.19 or later. For new environments on an old Python, do this right after creating them.
- Rebuild container images with layer caching disabled and update pinned certifi versions.
Only after updating Python, or after securely installing pip 26.2.2, update pip and certifi in each environment:
python3 -m pip install --upgrade pip certifi
For Python installed from the python.org macOS installer, Python gives this command (adjust the version number to your installation):
/Library/Frameworks/Python.framework/Versions/3.15/bin/python3.15 -m pip install --upgrade certifi
uv users can update using the system certificates:
UV_SYSTEM_CERTS=true uv self update
Python also recommends these minimum versions: uv 0.13.6, conda 26.9.4, pixi 0.82.1, virtualenv 21.14.12, pipx 1.18.7, pipenv 2026.10.2, PDM 2.29.4, Pex 2.105.1, Hatch 1.18.2, pyenv 2.8.14, sigstore 4.5.1, cibuildwheel 4.3.5, pypa/gh-action-pypi-publish 1.14.3, python-build-standalone 20261026, and manylinux and musllinux images 2026.10.26-1. Python 3.10 and older will not get a fix, so plan a move to a supported version.
What if you may already be compromised
Neither Python nor GitHub has published indicators of compromise, and no exploitation is known so far. An attack would also require the attacker to hold one of the leaked keys and control your network connection at the same time.
- Find out where and when packages were installed. Installs from untrusted networks, such as public Wi-Fi, deserve the closest look.
- Compare installed packages against the hashes in your locked dependency files. If in doubt, rebuild the environment from scratch.
- If your applications or pip sent passwords or tokens, for example to a private package index or an API, consider rotating them.
- If you have logs from a proxy or firewall with TLS inspection, look for eMudhra or emSign certificates on domains where they should not appear.
If you find unknown code, unexpected changes in applications or suspicious network traffic, bring in an incident response specialist before you start cleaning up the system.
Sources
- Mailman 3 [CVE-2026-133949] pip bundles compromised eMudhra certificates via certifi - Sec ↗
- Information for Python users regarding eMudhra / emSign CA certificate security incident - ↗
- certifi bundles emSign root CAs with compromised intermediate CA keys · GHSA-6q48-6c7w-9gw ↗
- NVD: CVE-2026-133949 ↗
- ENISA EUVD EUVD-2026-131829 ↗