Repository navigation
fix: update certifi, uv and Go (eMudhra intermediate CA compromise) - #7998
Merged
Merged
Conversation
See https://emudhra.we-have-a-problem.com/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| [[package]] | ||
| name = "certifi" | ||
| version = "2026.6.17" | ||
| version = "2026.10.19" |
Contributor
There was a problem hiding this comment.
🟨 Deployed examples retain vulnerable trust roots
When examples build, uv sync cannot use the patched certifi pin because the build context excludes the workspace lockfile. The unchanged livekit-agents dependency floor permits the compromised trust roots in deployed agents.
Was this helpful? React with 👍 or 👎 to provide feedback.
longcw
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
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.
The private keys of eight eMudhra intermediate CAs have been compromised (disclosed 2026-10-20: https://emudhra.we-have-a-problem.com/). The intermediates chain to
emSign Root TLS CA - G3and, through a Sectigo cross-sign, toAAA Certificate Services. Anyone holding those keys can issue a certificate for any hostname.Browsers already block the intermediates. Clients that ship their own trust store or verifier do not, until they take a patched release. This PR moves this repo onto those patched releases.
Changes
uv.lock:certifi2026.6.17 → 2026.10.19, which removes the affected roots. This is the only package changed (uv lock --upgrade-package certifi, run with uv 0.13.4).examples/*/Dockerfile:ghcr.io/astral-sh/uv:0.11.6→0.13.4, the patched uv.tests/Dockerfile.toxiproxy:golang:1.25-alpine→golang:1.27-alpine. Go 1.25 is out of support and gets nocrypto/x509fix. The1.27tag resolves to 1.27.3 or later.Not covered here
certififloor in published package metadata is unchanged. Downstream users get the fix from their own lockfile orpip install -U certifi.🤖 Generated with Claude Code