I use Python packages and containers. Which updates address the certificate issue, and do existing virtual environments need separate attention?
What should Python users update after the eMudhra certificate incident?
Answers
Update affected tools to at least certifi 2026.10.19, pip 26.2.2, uv 0.13.4 and sigstore 4.5.1, wherever you use them. The certifi version listed here is newer than the one in its advisory and is recommended for compatibility with unaffected emSign roots.
The issue is that an affected certificate in a trusted CA bundle could allow TLS interception. Updating removes the affected trust, rather than fixing a problem in your application code.
Reply to this answer
Check each existing virtual environment. Updating the system Python or its packages doesn't automatically update the copies inside those environments. Upgrade pip and uv where present, and update certifi if the environment uses it.
Reply to this answer
For containers, rebuild the images so they pick up updated system certificates and Python dependencies, then replace the deployed images. Watch the build cache too. A cached layer can leave an old package in place even after you start a rebuild, so a no-cache build may be needed.
Reply to this answer
There is an awkward bootstrap problem here. An old pip may be used to download its own update while it still trusts the affected certificate. Consider obtaining the updated package through a known good source and verifying its integrity, rather than assuming the vulnerable download path is safe.
MEXORA.7k:
So just creating a fresh environment isn't necessarily enough if its initial pip is still old?
8k~tumblefob_731:
Right. Check the version in the new environment and upgrade it if needed.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_e83+plumferrule.5:
New environments also deserve a check. The pip initially installed by the environment creator may itself need an upgrade.