critical

GHSA-hq85-5cpj-mr62

uv's bundled CA store trusts an emSign root whose intermediate CA keys are compromised

Published 20 Oct 2026Modified 20 Oct 2026

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

GHSA9.1CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Trivy's own label is CRITICAL. Rated critical by GHSA.

Description

By default, uv verifies TLS connections against a vendored copy of the `webpki-root-certs` bundle. Versions before 0.13.4 include the `emSign ECC Root CA - G3` root. Eight eMudhra intermediate CA certificates that chain to that root have compromised private keys, and the CA has revoked them. An attacker with one of the compromised keys can issue certificates that uv accepts for any hostname, and can be used to issue certificates to enable MITM attacks. uv 0.13.4 removes the root from its vendored bundle, following `webpki-root-certs` 1.0.10. Upgrade to 0.13.4 or later.

Affected packages and fixed versions

Source	Package	Fixed in
pip::GitHub Security Advisory pip	uv	0.13.4
rapidfort alpine 3.20	uv	no fix listed
rapidfort alpine 3.21	uv	no fix listed
rapidfort alpine 3.22	uv	no fix listed
rapidfort alpine 3.23	uv	no fix listed
rapidfort alpine 3.24	uv	no fix listed
rapidfort fedora 43	python3-uv, uv	0.13.5-2.fc43
rapidfort Oracle Linux 10	python3-uv, uv	0.13.5-2.el10_4

Show all 10 entries from 8 sources

Source	Package	Fixed in
pip::GitHub Security Advisory pip	uv	0.13.4
rapidfort alpine 3.20	uv	no fix listed
rapidfort alpine 3.21	uv	no fix listed
rapidfort alpine 3.22	uv	no fix listed
rapidfort alpine 3.23	uv	no fix listed
rapidfort alpine 3.24	uv	no fix listed
rapidfort fedora 43	python3-uv	0.13.5-2.fc43
rapidfort fedora 43	uv	0.13.5-2.fc43
rapidfort Oracle Linux 10	python3-uv	0.13.5-2.el10_4
rapidfort Oracle Linux 10	uv	0.13.5-2.el10_4

References

What Attestkeep does with this

Inside your cluster, without you opening a spreadsheet.

KnowsThe scanner refreshes its vulnerability database every six hours.

FindsEvery admitted image is rescanned every 24 hours by default (scan.rescanInterval). When Trivy rates this vulnerability critical for the image's package source, it appears in the image's findings by name. Findings without a fix are left out unless includeUnfixed is on.

Tells youA critical_finding event goes to the channels subscribed to it: e-mail, Slack, Teams, a webhook, Jira, GitLab or GitHub.

RefusesWith a policy that blocks critical findings, a pod with this image is refused at admission, a rollback to it included. Pods already running are not evicted.

RecordsEach decision is recorded with the policy that ran and its hash, then sealed under a signed checkpoint.

Try Attestkeep

Read the docs