Repository navigation
fix(deps): stop trusting the compromised eMudhra CAs (certifi, uv, pip) - #76
Merged
brendan-priorlabs merged 1 commit intoOct 21, 2026
Merged
Conversation
Bump the tools that bundle their own CA roots to the releases that drop the emSign roots: certifi 2026.10.19, pip 26.2.2, uv 0.13.4 and pypa/gh-action-pypi-publish v1.14.3. https://discuss.python.org/t/information-for-python-users-regarding-emudhra-emsign-ca-certificate-security-incident/109576 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
brendan-priorlabs
marked this pull request as ready for review
October 21, 2026 16:20
eddiebergman-priorlabs
approved these changes
Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The private keys of eight eMudhra (emSign) intermediate CAs were compromised, so anyone can mint a certificate
for any domain that chains to them. Python tools with bundled trust stores (certifi, pip's vendored certifi, uv's
embedded webpki roots) keep trusting them until upgraded. That enables a man-in-the-middle on pypi.org,
files.pythonhosted.org and any HTTPS API our code calls.
Fixed versions: certifi 2026.10.19, pip 26.2.2, uv 0.13.4, sigstore 4.5.1, pypa/gh-action-pypi-publish v1.14.3.
What this PR changes
pyproject.toml: exempt certifi from the exclude-newer cooldownuv.lock: certifi 2026.7.22 -> 2026.10.19The relock was done with uv 0.13.4, which writes lock
revision = 5and simplifies some markers. Older uv reads it fine. No package versions change except the ones listed.After merge
This PR was generated mechanically (one of many across the org). Tracking:
certfix/status.pyin q task202610211424-consider-we-d-like-to.🤖 Generated with Claude Code