Repository navigation
fix: distrust the compromised eMudhra intermediate CAs - #149
Merged
Merged
Conversation
Eight eMudhra intermediate CAs had recoverable private keys and are now distrusted (https://emudhra.we-have-a-problem.com/). Clients that do not enforce Certificate Transparency, like requests and curl, still trusted them through the bundles baked into this image. - certifi 2026.7.22 -> 2026.10.19 (locked with uv 0.6.5, same as the build) - upgrade ca-certificates in the runtime stage; python:3.10-alpine ships 20260909-r0, the fix is 20261020-r0
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
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
Eight eMudhra intermediate CAs had recoverable private keys and are now distrusted by browsers and trust stores (disclosure). Clients that do not enforce Certificate Transparency (requests, urllib, curl) still trusted them via the bundles baked into this image, so outbound TLS could be MITMed.
Changes
uv.lock: certifi2026.7.22->2026.10.19(3-line diff, locked with uv 0.6.5 to match the Dockerfile)Dockerfile:apk upgrade ca-certificates ca-certificates-bundlein the runtime stage (python:3.10-alpineships20260909-r0, fix is20261020-r0)Verification
Built the auth-service image locally (linux/amd64):
requests/urllib/curltodv-g3b-emudhra.we-have-a-problem.com-> SSL error; topypi.org-> 200ca-certificates-20261020-r0,certifi 2026.10.19