Repository navigation
Update rustls-webpki after the eMudhra incident - #22777
Conversation
Merging this PR will improve performance by 16.2%
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ⚡ | CPU Simulation | imbibe_marker_no_conflicts[0] |
398.5 ns | 343 ns | +16.2% |
Tip
Curious why performance improved? Comment @codspeedbot explain why performance improved on this PR, or directly use the CodSpeed MCP with your agent.
Comparing alex/emudhra-security (6b119ca) with main (aaac466)
Footnotes
-
54 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩
woodruffw
left a comment
There was a problem hiding this comment.
Cool, that's a nice defense-in-depth.
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [ghcr.io/astral-sh/uv](https://github.com/astral-sh/uv) | stage | patch | `0.13.1` → `0.13.5` | --- ### Release Notes <details> <summary>astral-sh/uv (ghcr.io/astral-sh/uv)</summary> ### [`v0.13.5`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0135) [Compare Source](astral-sh/uv@0.13.4...0.13.5) Released on 2026-10-21. Following [uv 0.13.4](https://github.com/astral-sh/uv/releases/tag/0.13.4), which removed the affected eMudhra/emSign root from uv's own certificate store, this release updates the latest managed CPython builds for 3.11 and newer to [python-build-standalone 20261021](https://github.com/astral-sh/python-build-standalone/releases/tag/20261021), including the CPython [3.15.1](https://www.python.org/downloads/release/python-3151/), [3.14.9](https://www.python.org/downloads/release/python-3149/), and [3.13.17](https://www.python.org/downloads/release/python-31317/) security patch releases. These builds include [pip 26.2.2](https://pip.pypa.io/en/stable/news/#v26-2-2) both preinstalled in the managed interpreter and bundled with `ensurepip`, which installs pip by default when you run `python -m venv`. Both copies use certifi 2026.10.19, which removes the same affected root. After upgrading uv, run `uv python upgrade` to install the updated builds. Virtual environments pinned to an older Python patch version do not switch to the updated interpreter automatically. Upgrade pip separately in existing virtual environments. Please note upstream CPython 3.9 and 3.10 still bundle pip releases whose certificate bundles trust the affected eMudhra/emSign root. We recommend migrating off of those versions and will no longer be releasing Docker images with uv installed for EOL Python versions. ##### Enhancements - Report incompatible self-dependencies directly in resolution errors ([#​21845](astral-sh/uv#21845)) ##### Python - Add CPython 3.15.1, 3.14.9, and 3.13.17 ([#​22802](astral-sh/uv#22802)) ##### Preview features - Select and rank wheel variants with no required properties or properties from PEP 850 static providers in platform-specific resolutions with `wheel-variants` ([#​22535](astral-sh/uv#22535), [#​22536](astral-sh/uv#22536), [#​22687](astral-sh/uv#22687), [#​22688](astral-sh/uv#22688)) ##### Performance - Reduce peak memory use when resolving dependencies across multiple environments ([#​22769](astral-sh/uv#22769), [#​22770](astral-sh/uv#22770), [#​22784](astral-sh/uv#22784)) - Speed up exports with complex transitive extras by resolving activation across the dependency graph ([#​22751](astral-sh/uv#22751)) - Reduce uv's binary size by keeping additional error formatters out of line ([#​22775](astral-sh/uv#22775)) - Reduce overhead when parsing custom build cache keys ([#​22749](astral-sh/uv#22749)) ##### Bug fixes - Lock packages distributed only as Android wheels without a source distribution ([#​22806](astral-sh/uv#22806)) - Export optional dependencies correctly when transitive extras are activated through different or incompatible environment paths ([#​22751](astral-sh/uv#22751)) - Reject invalid custom build cache keys instead of silently falling back to the defaults ([#​22749](astral-sh/uv#22749)) ##### Security - Reject certificate chains containing compromised eMudhra intermediate keys via `rustls-webpki` 0.103.16 ([#​22777](astral-sh/uv#22777)) - Stop publishing uv Docker images based on Python 3.9 and 3.10 images that no longer receive upstream updates ([#​22773](astral-sh/uv#22773)) ### [`v0.13.4`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0134) [Compare Source](astral-sh/uv@0.13.3...0.13.4) Released on 2026-10-20. ##### Preview features - Validate PEP 825 variant metadata and treat package versions with invalid metadata as unavailable under `wheel-variants` ([#​22512](astral-sh/uv#22512)) ##### Other changes - Update the bundled Mozilla root certificates via `webpki-root-certs` 1.0.10 ([#​22760](astral-sh/uv#22760)) ### [`v0.13.3`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0133) [Compare Source](astral-sh/uv@0.13.2...0.13.3) Released on 2026-10-20. ##### Performance - Avoid severe `uv export` slowdowns in dependency graphs with extras ([#​22750](astral-sh/uv#22750)) ### [`v0.13.2`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0132) [Compare Source](astral-sh/uv@0.13.1...0.13.2) Released on 2026-10-19. ##### Enhancements - Report all installed packages in `uv workspace metadata`, including packages outside the selected resolution ([#​22395](astral-sh/uv#22395)) - Include supported environment restrictions when exporting `pylock.toml` ([#​22596](astral-sh/uv#22596)) - Retry dropped GET and HEAD requests when fetching package and index data ([#​22672](astral-sh/uv#22672)) - Preserve encoding declarations in wheel data scripts that require shell launchers ([#​22526](astral-sh/uv#22526)) - Show causes and hints when `uv python find --script` cannot discover an interpreter, including with `-q` ([#​22549](astral-sh/uv#22549)) - Print valid ksh activation instructions and support non-relocatable environments under OpenBSD-derived ksh ([#​22538](astral-sh/uv#22538), [#​22572](astral-sh/uv#22572)) - Allow PEP 508 direct URLs, including Mercurial and extensionless archive URLs, in uv-build's `[build-system].requires` validation ([#​22577](astral-sh/uv#22577)) ##### Python - Add PyPy 3.11.17 and 3.12.15 ([#​22578](astral-sh/uv#22578)) ##### Preview features - Fetch and parse PEP 825 index-level variant metadata with `wheel-variants` ([#​22509](astral-sh/uv#22509), [#​22511](astral-sh/uv#22511)) ##### Performance - Avoid exponential work when simplifying, traversing, and exporting complex dependency markers ([#​22608](astral-sh/uv#22608), [#​22615](astral-sh/uv#22615), [#​22651](astral-sh/uv#22651), [#​22674](astral-sh/uv#22674)) - Reduce the time and memory used to parse and store complex dependency markers ([#​22675](astral-sh/uv#22675), [#​22676](astral-sh/uv#22676), [#​22681](astral-sh/uv#22681)) - Reduce resolver memory use for large dependency graphs, forks, extras, and dependency groups ([#​22565](astral-sh/uv#22565), [#​22625](astral-sh/uv#22625)) - Speed up project discovery in large workspaces by caching member names ([#​22635](astral-sh/uv#22635)) - Reduce uv's binary size and speed up CycloneDX exports ([#​22431](astral-sh/uv#22431)) - Reduce `uv-build` binary size, including Linux x86_64 wheels ([#​22539](astral-sh/uv#22539), [#​22573](astral-sh/uv#22573)) - Reduce allocations when parsing TOML ([#​22679](astral-sh/uv#22679)) ##### Bug fixes - Respect `--exclude-newer` when a newer wheel for the selected source distribution is already cached ([#​22685](astral-sh/uv#22685)) - Prevent URL credentials from leaking through diagnostics or persisted metadata ([#​22600](astral-sh/uv#22600), [#​22601](astral-sh/uv#22601), [#​22617](astral-sh/uv#22617), [#​22622](astral-sh/uv#22622), [#​22646](astral-sh/uv#22646)) - Keep separate cache entries for signed `--find-links` URLs that differ only in sensitive query values ([#​22630](astral-sh/uv#22630)) - Honor PEP 751 environment restrictions when installing or syncing from `pylock.toml` ([#​22594](astral-sh/uv#22594)) - Use configured credentials before prompting during `uv publish`, and avoid prompting when no upload occurs ([#​22593](astral-sh/uv#22593)) - Match recursive build globs against complete file paths and ignore invalid license symlinks ([#​22581](astral-sh/uv#22581), [#​22583](astral-sh/uv#22583)) - Return an error for invalid `uv pip compile --python-version` values instead of panicking ([#​22727](astral-sh/uv#22727)) - Reject invalid `pylock.toml` output filenames before resolution instead of panicking ([#​22725](astral-sh/uv#22725)) - Avoid panicking during repeated resolution conflicts involving fixed-priority packages ([#​22589](astral-sh/uv#22589)) - Create version aliases correctly when installing managed Python into a relative directory ([#​22547](astral-sh/uv#22547)) - Show incompatibilities from failing `uv pip check` invocations with `-q` ([#​22544](astral-sh/uv#22544)) - Treat logically equivalent dependency markers as equal regardless of construction order ([#​22680](astral-sh/uv#22680)) ##### Rust API - Require the opt-in `unsafe-url` feature to use raw `url::Url` APIs in `uv-pep508` ([#​22623](astral-sh/uv#22623)) ##### Documentation - Clarify credential lookup, environment synchronization, managed Python, and integration guidance ([#​22542](astral-sh/uv#22542)) ##### Other changes - Use stable `sh.astral.*` signing identifiers for macOS binaries ([#​22648](astral-sh/uv#22648)) </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xNjAuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjE2MC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJ0eXBlL2RlcGVuZGVuY2llcyJdfQ==--> Reviewed-on: https://git.tainton.uk/repos/rsu/pulls/61 Co-authored-by: renovate[bot] <renovate-bot@git.tainton.uk>
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [uv](https://github.com/astral-sh/uv) | tools | patch | `0.13.4` → `0.13.5` | --- ### Release Notes <details> <summary>astral-sh/uv (uv)</summary> ### [`v0.13.5`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0135) [Compare Source](astral-sh/uv@0.13.4...0.13.5) Released on 2026-10-21. Following [uv 0.13.4](https://github.com/astral-sh/uv/releases/tag/0.13.4), which removed the affected eMudhra/emSign root from uv's own certificate store, this release updates the latest managed CPython builds for 3.11 and newer to [python-build-standalone 20261021](https://github.com/astral-sh/python-build-standalone/releases/tag/20261021), including the CPython [3.15.1](https://www.python.org/downloads/release/python-3151/), [3.14.9](https://www.python.org/downloads/release/python-3149/), and [3.13.17](https://www.python.org/downloads/release/python-31317/) security patch releases. These builds include [pip 26.2.2](https://pip.pypa.io/en/stable/news/#v26-2-2) both preinstalled in the managed interpreter and bundled with `ensurepip`, which installs pip by default when you run `python -m venv`. Both copies use certifi 2026.10.19, which removes the same affected root. After upgrading uv, run `uv python upgrade` to install the updated builds. Virtual environments pinned to an older Python patch version do not switch to the updated interpreter automatically. Upgrade pip separately in existing virtual environments. Please note upstream CPython 3.9 and 3.10 still bundle pip releases whose certificate bundles trust the affected eMudhra/emSign root. We recommend migrating off of those versions and will no longer be releasing Docker images with uv installed for EOL Python versions. ##### Enhancements - Report incompatible self-dependencies directly in resolution errors ([#​21845](astral-sh/uv#21845)) ##### Python - Add CPython 3.15.1, 3.14.9, and 3.13.17 ([#​22802](astral-sh/uv#22802)) ##### Preview features - Select and rank wheel variants with no required properties or properties from PEP 850 static providers in platform-specific resolutions with `wheel-variants` ([#​22535](astral-sh/uv#22535), [#​22536](astral-sh/uv#22536), [#​22687](astral-sh/uv#22687), [#​22688](astral-sh/uv#22688)) ##### Performance - Reduce peak memory use when resolving dependencies across multiple environments ([#​22769](astral-sh/uv#22769), [#​22770](astral-sh/uv#22770), [#​22784](astral-sh/uv#22784)) - Speed up exports with complex transitive extras by resolving activation across the dependency graph ([#​22751](astral-sh/uv#22751)) - Reduce uv's binary size by keeping additional error formatters out of line ([#​22775](astral-sh/uv#22775)) - Reduce overhead when parsing custom build cache keys ([#​22749](astral-sh/uv#22749)) ##### Bug fixes - Lock packages distributed only as Android wheels without a source distribution ([#​22806](astral-sh/uv#22806)) - Export optional dependencies correctly when transitive extras are activated through different or incompatible environment paths ([#​22751](astral-sh/uv#22751)) - Reject invalid custom build cache keys instead of silently falling back to the defaults ([#​22749](astral-sh/uv#22749)) ##### Security - Reject certificate chains containing compromised eMudhra intermediate keys via `rustls-webpki` 0.103.16 ([#​22777](astral-sh/uv#22777)) - Stop publishing uv Docker images based on Python 3.9 and 3.10 images that no longer receive upstream updates ([#​22773](astral-sh/uv#22773)) </details> --- ### Configuration 📅 **Schedule**: (in timezone Europe/London) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xNjcuNSIsInVwZGF0ZWRJblZlciI6IjQ0LjE2Ny41IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZS9naXRodWItcmVsZWFzZSIsInR5cGUvcGF0Y2giXX0=--> Reviewed-on: https://git.hayden.moe/hayden/phoebe/pulls/943
uv 0.13.4 only updated the bundled Mozilla roots (webpki-root-certs 1.0.10, astral-sh/uv#22760), which removes the emSign root. uv 0.13.5 rejects certificate chains that contain the compromised eMudhra intermediate keys (rustls-webpki 0.103.16, astral-sh/uv#22777), so it also covers any chain through a root that remains in the bundle. Both hosts of this site are rejected by 0.13.5 with CertDistrusted.
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [ghcr.io/astral-sh/uv](https://github.com/astral-sh/uv) | final | patch | `0.13.1` → `0.13.5` | --- ### Release Notes <details> <summary>astral-sh/uv (ghcr.io/astral-sh/uv)</summary> ### [`v0.13.5`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0135) [Compare Source](astral-sh/uv@0.13.4...0.13.5) Released on 2026-10-21. Following [uv 0.13.4](https://github.com/astral-sh/uv/releases/tag/0.13.4), which removed the affected eMudhra/emSign root from uv's own certificate store, this release updates the latest managed CPython builds for 3.11 and newer to [python-build-standalone 20261021](https://github.com/astral-sh/python-build-standalone/releases/tag/20261021), including the CPython [3.15.1](https://www.python.org/downloads/release/python-3151/), [3.14.9](https://www.python.org/downloads/release/python-3149/), and [3.13.17](https://www.python.org/downloads/release/python-31317/) security patch releases. These builds include [pip 26.2.2](https://pip.pypa.io/en/stable/news/#v26-2-2) both preinstalled in the managed interpreter and bundled with `ensurepip`, which installs pip by default when you run `python -m venv`. Both copies use certifi 2026.10.19, which removes the same affected root. After upgrading uv, run `uv python upgrade` to install the updated builds. Virtual environments pinned to an older Python patch version do not switch to the updated interpreter automatically. Upgrade pip separately in existing virtual environments. Please note upstream CPython 3.9 and 3.10 still bundle pip releases whose certificate bundles trust the affected eMudhra/emSign root. We recommend migrating off of those versions and will no longer be releasing Docker images with uv installed for EOL Python versions. ##### Enhancements - Report incompatible self-dependencies directly in resolution errors ([#​21845](astral-sh/uv#21845)) ##### Python - Add CPython 3.15.1, 3.14.9, and 3.13.17 ([#​22802](astral-sh/uv#22802)) ##### Preview features - Select and rank wheel variants with no required properties or properties from PEP 850 static providers in platform-specific resolutions with `wheel-variants` ([#​22535](astral-sh/uv#22535), [#​22536](astral-sh/uv#22536), [#​22687](astral-sh/uv#22687), [#​22688](astral-sh/uv#22688)) ##### Performance - Reduce peak memory use when resolving dependencies across multiple environments ([#​22769](astral-sh/uv#22769), [#​22770](astral-sh/uv#22770), [#​22784](astral-sh/uv#22784)) - Speed up exports with complex transitive extras by resolving activation across the dependency graph ([#​22751](astral-sh/uv#22751)) - Reduce uv's binary size by keeping additional error formatters out of line ([#​22775](astral-sh/uv#22775)) - Reduce overhead when parsing custom build cache keys ([#​22749](astral-sh/uv#22749)) ##### Bug fixes - Lock packages distributed only as Android wheels without a source distribution ([#​22806](astral-sh/uv#22806)) - Export optional dependencies correctly when transitive extras are activated through different or incompatible environment paths ([#​22751](astral-sh/uv#22751)) - Reject invalid custom build cache keys instead of silently falling back to the defaults ([#​22749](astral-sh/uv#22749)) ##### Security - Reject certificate chains containing compromised eMudhra intermediate keys via `rustls-webpki` 0.103.16 ([#​22777](astral-sh/uv#22777)) - Stop publishing uv Docker images based on Python 3.9 and 3.10 images that no longer receive upstream updates ([#​22773](astral-sh/uv#22773)) ### [`v0.13.4`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0134) [Compare Source](astral-sh/uv@0.13.3...0.13.4) Released on 2026-10-20. ##### Preview features - Validate PEP 825 variant metadata and treat package versions with invalid metadata as unavailable under `wheel-variants` ([#​22512](astral-sh/uv#22512)) ##### Other changes - Update the bundled Mozilla root certificates via `webpki-root-certs` 1.0.10 ([#​22760](astral-sh/uv#22760)) ### [`v0.13.3`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0133) [Compare Source](astral-sh/uv@0.13.2...0.13.3) Released on 2026-10-20. ##### Performance - Avoid severe `uv export` slowdowns in dependency graphs with extras ([#​22750](astral-sh/uv#22750)) ### [`v0.13.2`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0132) [Compare Source](astral-sh/uv@0.13.1...0.13.2) Released on 2026-10-19. ##### Enhancements - Report all installed packages in `uv workspace metadata`, including packages outside the selected resolution ([#​22395](astral-sh/uv#22395)) - Include supported environment restrictions when exporting `pylock.toml` ([#​22596](astral-sh/uv#22596)) - Retry dropped GET and HEAD requests when fetching package and index data ([#​22672](astral-sh/uv#22672)) - Preserve encoding declarations in wheel data scripts that require shell launchers ([#​22526](astral-sh/uv#22526)) - Show causes and hints when `uv python find --script` cannot discover an interpreter, including with `-q` ([#​22549](astral-sh/uv#22549)) - Print valid ksh activation instructions and support non-relocatable environments under OpenBSD-derived ksh ([#​22538](astral-sh/uv#22538), [#​22572](astral-sh/uv#22572)) - Allow PEP 508 direct URLs, including Mercurial and extensionless archive URLs, in uv-build's `[build-system].requires` validation ([#​22577](astral-sh/uv#22577)) ##### Python - Add PyPy 3.11.17 and 3.12.15 ([#​22578](astral-sh/uv#22578)) ##### Preview features - Fetch and parse PEP 825 index-level variant metadata with `wheel-variants` ([#​22509](astral-sh/uv#22509), [#​22511](astral-sh/uv#22511)) ##### Performance - Avoid exponential work when simplifying, traversing, and exporting complex dependency markers ([#​22608](astral-sh/uv#22608), [#​22615](astral-sh/uv#22615), [#​22651](astral-sh/uv#22651), [#​22674](astral-sh/uv#22674)) - Reduce the time and memory used to parse and store complex dependency markers ([#​22675](astral-sh/uv#22675), [#​22676](astral-sh/uv#22676), [#​22681](astral-sh/uv#22681)) - Reduce resolver memory use for large dependency graphs, forks, extras, and dependency groups ([#​22565](astral-sh/uv#22565), [#​22625](astral-sh/uv#22625)) - Speed up project discovery in large workspaces by caching member names ([#​22635](astral-sh/uv#22635)) - Reduce uv's binary size and speed up CycloneDX exports ([#​22431](astral-sh/uv#22431)) - Reduce `uv-build` binary size, including Linux x86_64 wheels ([#​22539](astral-sh/uv#22539), [#​22573](astral-sh/uv#22573)) - Reduce allocations when parsing TOML ([#​22679](astral-sh/uv#22679)) ##### Bug fixes - Respect `--exclude-newer` when a newer wheel for the selected source distribution is already cached ([#​22685](astral-sh/uv#22685)) - Prevent URL credentials from leaking through diagnostics or persisted metadata ([#​22600](astral-sh/uv#22600), [#​22601](astral-sh/uv#22601), [#​22617](astral-sh/uv#22617), [#​22622](astral-sh/uv#22622), [#​22646](astral-sh/uv#22646)) - Keep separate cache entries for signed `--find-links` URLs that differ only in sensitive query values ([#​22630](astral-sh/uv#22630)) - Honor PEP 751 environment restrictions when installing or syncing from `pylock.toml` ([#​22594](astral-sh/uv#22594)) - Use configured credentials before prompting during `uv publish`, and avoid prompting when no upload occurs ([#​22593](astral-sh/uv#22593)) - Match recursive build globs against complete file paths and ignore invalid license symlinks ([#​22581](astral-sh/uv#22581), [#​22583](astral-sh/uv#22583)) - Return an error for invalid `uv pip compile --python-version` values instead of panicking ([#​22727](astral-sh/uv#22727)) - Reject invalid `pylock.toml` output filenames before resolution instead of panicking ([#​22725](astral-sh/uv#22725)) - Avoid panicking during repeated resolution conflicts involving fixed-priority packages ([#​22589](astral-sh/uv#22589)) - Create version aliases correctly when installing managed Python into a relative directory ([#​22547](astral-sh/uv#22547)) - Show incompatibilities from failing `uv pip check` invocations with `-q` ([#​22544](astral-sh/uv#22544)) - Treat logically equivalent dependency markers as equal regardless of construction order ([#​22680](astral-sh/uv#22680)) ##### Rust API - Require the opt-in `unsafe-url` feature to use raw `url::Url` APIs in `uv-pep508` ([#​22623](astral-sh/uv#22623)) ##### Documentation - Clarify credential lookup, environment synchronization, managed Python, and integration guidance ([#​22542](astral-sh/uv#22542)) ##### Other changes - Use stable `sh.astral.*` signing identifiers for macOS binaries ([#​22648](astral-sh/uv#22648)) </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xNjAuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjE2MC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJ0eXBlL2RlcGVuZGVuY2llcyJdfQ==--> Reviewed-on: https://git.tainton.uk/repos/labmcp/pulls/81 Reviewed-by: Luke Tainton <luke@tainton.uk> Co-authored-by: renovate[bot] <renovate-bot@git.tainton.uk>
…'t hold any of the three roots (WOR-1116) CodeRabbit on 3549072 (Major): #756's entry told pipx's uv-backend users to upgrade uv to 0.13.4, and told users of a custom or system store to check only for "the affected root". 0.13.4 only drops emSign ECC Root CA - G3 from uv's built-in list; rejecting the compromised keys themselves starts in 0.13.5 (rustls-webpki 0.103.16, astral-sh/uv#22777). A store that still holds AAA Certificate Services lets a 0.13.4 accept the keys through Sectigo's cross-signatures. The entry now asks for 0.13.5 or later, says 0.13.5+ keeps rejecting the keys with SSL_CERT_FILE / SSL_CERT_DIR / system certificates, except on macOS or Windows with system certificates on (rustls-platform-verifier 0.7.0 hands the check to the OS there; elsewhere it wraps rustls-webpki), and names all three roots to check the store for. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…he roots above the compromised eMudhra keys (WOR-1116) (#758) `curl worthless.sh | sh` now downloads Worthless with uv 0.13.7, which trusts none of the certificate roots above the compromised eMudhra keys, and runs Worthless on Python 3.14.10 or a later 3.14. Closes WOR-1116. #756 merged first, so this PR also fixes #756's CHANGELOG entry: it drops the sentence that said install.sh still installs uv 0.11.7, and its advice for uv users now asks for 0.13.5 or later and names all three roots to keep out of a custom store, and links the oss-security notice's list of compromised intermediates to keep out too. ## Why install.sh installs its own pinned uv, then uses that uv to download Worthless and its dependencies from PyPI. The pin was uv 0.11.7, and install.sh puts it in place even over a newer uv you already have. uv checks PyPI's certificate against **its own built-in list of roots**, not your system's. uv before 0.13.4 trusts emSign ECC Root CA - G3, one of the three roots above the eMudhra intermediate keys disclosed as compromised in October ([GHSA-hq85-5cpj-mr62](GHSA-hq85-5cpj-mr62) for uv, [GHSA-6q48-6c7w-9gw2](GHSA-6q48-6c7w-9gw2) for certifi, both critical). Someone on the user's network path holding a certificate from one of those keys could serve the install a fake Worthless or a fake dependency. #756's certifi floor protects the proxy **after** the install. It can't protect the download that performs the install. CodeRabbit found this gap on #756. ## What The uv that install.sh installs moves from 0.11.7 to **0.13.7**, the latest release: - uv 0.13.4 dropped the affected root from uv's list ([astral-sh/uv#22760](astral-sh/uv#22760)). - uv 0.13.5 also rejects any chain containing the compromised keys, whatever root it ends at ([astral-sh/uv#22777](astral-sh/uv#22777)). What that means for a download. eMudhra's test site `testevg3.emsign.com` has a certificate chain that ends at emSign ECC Root CA - G3, the same shape a certificate from the compromised keys would have. Running `uv tool install worthless` with each uv, with this site as the package index: ``` uv 0.11.7: × No solution found ... worthless was not found in the package registry (TLS accepted; uv read whatever the server answered) uv 0.13.7: error: Failed to fetch: https://testevg3.emsign.com/simple/worthless/ cause: invalid peer certificate: UnknownIssuer ``` **install.sh also asks uv for Python 3.14.10 or a later 3.14** (`>=3.14.10,<3.15`). 3.14 is the series uv 0.11.7 picked on its own. Left to choose, uv 0.13 picks 3.15. PyYAML (pulled in by `uvicorn[standard]`) has no 3.15 wheel, so the install would build it from source, running setuptools and Cython fetched from PyPI on the spot with the caller's `CC`. On 3.14, every dependency installs from a wheel. **3.14.10's `ssl` module also rejects chains through the compromised keys.** A bare `3.14` request would keep an older uv-managed 3.14: a returning user's 3.14.4 stayed 3.14.4. The floor moves it to 3.14.10, downloading it if needed. 3.14.10 builds exist for macOS and for Linux glibc and musl, x86_64 and aarch64. A real install from this branch into an empty HOME: ``` $ env -i HOME=$(mktemp -d) PATH=/usr/bin:/bin:/usr/sbin:/sbin sh ./install.sh Platform: macos uv 0.12.10 found; bootstrapping pinned uv 0.13.7 worthless 0.3.16 Done! 'worthless' is installed. $ ~/.local/bin/uv --version uv 0.13.7 (316c827e0 2026-11-03 aarch64-apple-darwin) $ ~/.local/share/uv/tools/worthless/bin/python --version Python 3.14.10 nothing built from source (uv's sdist cache is empty); PyYAML has its C extension, so it came from a wheel ``` A returning user, simulated by a HOME that already has worthless 0.3.15 on a uv-managed Python 3.14.4, running this install.sh: ``` before: Python 3.14.4, worthless 0.3.15 uv 0.13.7 already installed worthless 0.3.16 after: Python 3.14.10, worthless 0.3.16 (a bare --python 3.14 left it on 3.14.4) ``` ## How - **`install.sh`:** - `UV_VERSION` 0.11.7 → 0.13.7, and `ASTRAL_INSTALLER_SHA256` → the SHA-256 of `https://astral.sh/uv/0.13.7/install.sh`. - `TOOL_PYTHON=">=3.14.10,<3.15"` sits next to `UV_VERSION`, with the reasoning. The install runs `uv tool install --force --python "$TOOL_PYTHON" worthless==<pin>`. - **New tests:** - `test_uv_version_rejects_compromised_emudhra_keys`: fails on dev (`(0, 11, 7) >= (0, 13, 6)`). The floor is 0.13.6, the first uv that downloads CPython 3.14.10. - `test_tool_python_keeps_the_3_14_10_floor` reads `TOOL_PYTHON` from install.sh itself, not the tests' copy, and requires 3.14.10+ and no 3.15. It fails on `"3.14"`, `">=3.14,<3.15"` and `">=3.14.10"`. - `test_default_install_pins_baked_version` now also requires the `--python` request. - `tests/live/test_install_uv_trust_live.py` (`-m live`). CI runs it in a new install-smoke job, "Pinned uv refuses the emSign G3 root and the compromised keys": - It installs the pinned uv the way install.sh does: Astral's installer, checked against the SHA-256. - It runs `uv tool install` with the pinned uv (not install.sh itself), with the emSign test site as the package index, and requires `UnknownIssuer`: the root is gone. - A second test serves CPython 3.14.10's test leaf, signed with the leaked EM OV TLS CA - G3C key, from localhost, and requires `CertDistrusted`: uv's block on the compromised keys themselves. It runs twice: with uv's built-in roots (the server also sends the test site's cross-certificate up to emSign ECC Root CA - G3, the chain someone holding the key could serve), and with emSign Root TLS CA - G3 given as a trust anchor, where the chain is valid apart from the key. CPython's `distrusted.zip` is fetched at v3.14.10's commit and checked by SHA-256, not committed, since it holds a private key. - All three fail on dev's uv 0.11.7, which completes TLS and reports "worthless was not found in the package registry", and pass on 0.13.7. - Run locally, they skip if the test site or CPython's file is gone, or the site no longer chains to that root. The CI job sets `WORTHLESS_UV_TRUST_REQUIRED=1`, so there a skip fails instead: a green job means the checks ran. - **Test stubs:** the fake uv in `test_install_logic.py` now reports `_UV_VERSION` instead of a literal, as `test_install_shadow_warning.py` already did. The next bump is one line in `tests/_install_helpers.py`. Three tests that pin the exact `tool install` arguments now include `--python {_TOOL_PYTHON}`, which `tests/_install_helpers.py` keeps in sync by hand with install.sh, like `_UV_VERSION`. `read_install_var(name)` there replaces three copies of the `NAME="..."` regex. - **Linux service fixture:** `Dockerfile.service-lifecycle-live-linux` sets `UV_PYTHON=3.14`. Its entrypoints `uv sync --frozen` the repo. Under uv 0.13 that picked 3.15, the locked `cffi==2.0.0` has no 3.15 wheel, and the image has no compiler. CI's "service lock roundtrip (Linux Docker)" failed on the first push for this reason. - **Version references:** the `?explain=1` walkthrough, the OpenClaw test images (which claim to use install.sh's uv), and the rendered terminal traces now say 0.13.7. The OpenClaw test image already moved to uv 0.13.7 and install.sh's Python in #762, now in dev, so after the merge this PR only trims a comment there. - **install-smoke CI:** before the real install.sh run on macOS and Ubuntu, the job puts an older uv-managed Python 3.14.4 on the runner, like a returning user's. After the run it requires Worthless's Python to be `>=3.14.10,<3.15`. Checked locally: with a weakened `>=3.14,<3.15`, uv reuses 3.14.4 and the check fails. - **CHANGELOG:** a new Unreleased/Security entry, placed after #756's. In #756's entry, the sentence that said install.sh still installs uv 0.11.7 is dropped, since this entry covers install.sh's uv now. Its uv advice also changes, after CodeRabbit's review: it asked pipx's uv-backend users for 0.13.4, which only drops one root, so it now asks for 0.13.5, the first uv that rejects the compromised keys themselves. It now says 0.13.5 keeps rejecting them under `SSL_CERT_FILE`, `SSL_CERT_DIR` or system certificates, except on macOS or Windows with system certificates on, where the operating system checks instead. And it asks users to check a custom store for all three roots and for the compromised intermediates themselves, not for one root: a store that trusts one of those intermediates directly lets uv 0.11.7 accept the key with none of the roots (checked by hand; uv 0.13.7 still refuses with `CertDistrusted`). Both store checks in #756's entry now link the [oss-security notice](https://www.openwall.com/lists/oss-security/2026/10/20/1), which lists the roots and the intermediates with their fingerprints. The merge with dev after #762 also adds one Limits sentence to #762's entry, which #762's merge council asked for in the commit that resolves this PR's conflict with it: if your user can't open `~/.openclaw`, the check crashes on Python 3.10 to 3.13, and on 3.14 its note names only the `main` agent's folder, so other agents get no note (WOR-1128). Checked on 3.13.15 and 3.14.7. ## What this does NOT do - **On macOS, and on Linux with an out-of-date `ca-certificates`, the first download is still exposed.** curl checks your system's list, which this PR doesn't change. The compromised keys chain to three roots ([oss-sec](https://seclists.org/oss-sec/2026/q4/233)): emSign ECC Root CA - G3, emSign Root TLS CA - G3, and, through Sectigo's cross-signatures, AAA Certificate Services. macOS's `/usr/bin/curl` uses `/etc/ssl/cert.pem`, which still has emSign ECC Root CA - G3 and AAA Certificate Services: it completed TLS to the emSign test site (`http=302 ssl_verify_result=0`). Current Debian 12 (security update `20250419~deb12u2`), Ubuntu 24.04 (`20260816ubuntu0.24.04.2`; the blacklist landed in `.1`) and Alpine (`ca-certificates-bundle-20261020-r0`) have none of the three. The `fedora:41` image's `ca-certificates-2024.2.69` still has emSign ECC Root CA - G3 and AAA Certificate Services, and Fedora 41's repos offer no newer one. uv 0.13.7 has none of the three roots, and 0.13.5+ rejects the compromised keys under any root, with one exception, next bullet. Someone holding those keys can still swap the install.sh piped into `sh`. This PR closes the uv hop, not the curl hop. - **With `UV_SYSTEM_CERTS` set on macOS, uv's own block on the compromised keys doesn't run.** install.sh doesn't clear that variable (WOR-1117). With it, uv 0.13.7 hands the check to macOS's verifier (rustls-platform-verifier), which uses macOS's list, still trusting two of the roots. Against the emSign test site that check said `Revoked`, so Apple's revocation data caught that chain, but uv's key block is not what stopped it. install.sh's proxy hints send corporate users to the system trust store, so this setup is plausible. The CHANGELOG has this as a Limit. - **Other checks on Python 3.14 still treat a folder they can't open as missing (WOR-1125).** On 3.14, `Path.is_file()` and `is_dir()` return `False` where they can't look; 3.10 to 3.13 raise `PermissionError`. #762, now in dev, fixed this for the OAuth-login check in `worthless lock` and `worthless doctor --json`. Elsewhere it remains: for example, `worthless status` shows a key whose `.env` sits in a folder your user can't open as BROKEN. This predates the PR: uv 0.11.7 also put Worthless on 3.14. - **The uv archive's SHA-256 is checked only if `sha256sum` exists.** install.sh checks the Astral installer's SHA-256, and the installer checks the uv archive's, but it silently skips that check when `sha256sum` isn't installed. Tracked in WOR-1117. - **`curl worthless.sh` serves the last release's install.sh.** The Worker deploys from a signed `v*` tag, so this reaches users with the next release. - **A uv that install.sh left behind earlier stays 0.11.7.** Running it yourself, for example `uv tool upgrade worthless`, still trusts the affected root. 0.11.7 also predates the entry-point file-write fix ([GHSA-4gg8-gxpx-9rph](GHSA-4gg8-gxpx-9rph), fixed in 0.11.15). Re-running install.sh after the next release replaces it. - **The Python moves only when install.sh installs a new Worthless version.** A re-run at the version you already have still updates uv but skips the tool install, so the tool keeps its old Python until the next release. Then it moves to 3.14.10, downloading it if needed. WOR-1119 makes a re-run enough. - **The env scrub still misses some uv variables.** These predate this PR: `UV_SYSTEM_CERTS`, `UV_OVERRIDE`/`UV_CONSTRAINT`/`UV_BUILD_CONSTRAINT`, `UV_PYTHON_DOWNLOADS_JSON_URL`, `UV_CACHE_DIR`, and `CC`/`LDSHARED` for any future source build. There is also `UV_PYTHON_INSTALL_DIR`: brutus showed a hostile rc file can use it to supply a planted "managed" 3.14.10 that meets the floor. uv 0.11.7 accepted the same directory. Filed as WOR-1117. --- <details><summary>Engineering detail</summary> - **Provenance (cooldown waived, owner's "take latest" rule for advisory bumps):** 0.13.7 was released 2026-11-03. - `https://astral.sh/uv/0.13.7/install.sh` is byte-identical to the `uv-installer.sh` asset on the GitHub release (`d263ee68…2db4`). - `gh attestation verify --repo astral-sh/uv` passes. The signer is `astral-sh/uv/.github/workflows/release.yml`, the same workflow that signed 0.11.7's installer, at commit `316c827e`, which is what tag `0.13.7` points at. - The installer embeds a SHA-256 per uv archive. They match the release's `sha256.sum` (checked for `uv-aarch64-apple-darwin.tar.gz`). - 0.13.5 → 0.13.7 is bug fixes plus new Python builds. - **Root lists in the binaries:** `emSign ECC Root CA - G3` is in uv 0.11.7 and gone from 0.13.7. Neither binary has `emSign Root TLS CA - G3` or `AAA Certificate Services`. Both still have emSign Root CA - G1, Root CA - C1 and ECC Root CA - C3, none of them a root the oss-security notice lists for the compromised keys. certifi 2026.10.23 (#756) dropped C1 and C3. - **uv 0.11.7 → 0.13.7 changes that touch install.sh:** I read uv's CHANGELOG for 0.12.0 and 0.13.0 (the two breaking releases) and every 0.13.x. install.sh calls only `uv --version`, `uv tool install`, `uv tool list` and `uv tool dir --bin`, and none of those changed except the default Python. 0.13.0 moved it to 3.15, which this PR answers with `--python ">=3.14.10,<3.15"`. - **Env scrub:** I diffed `crates/uv-static/src/env_vars.rs` at 0.11.7 and 0.13.7. 20 public `UV_*` names are new, and none redirects `uv tool install`: - `UV_MALWARE_CHECK_URL` only applies to the check after `uv sync`. - `UV_AZURE_ENDPOINT_URL` only signs requests to an index there, and the index variables that could point uv at one are already scrubbed. - `UV_PYTHON_SEARCH_PATH` only finds system interpreters, and install.sh forces `UV_PYTHON_PREFERENCE=only-managed`. - `UV_GRAALPY_INSTALL_MIRROR` and `UV_PYODIDE_INSTALL_MIRROR` only apply to those interpreters. - `UV_NO_SYSTEM_CONFIG` covers `/etc/uv`, which is root-owned. - The older gaps the review found are in WOR-1117. - **Tests:** `test_install_static.py`, `test_install_logic.py`, `test_install_shadow_warning.py`, `test_install_shellcheck.py` and `tests/user_flows/test_render_traces.py`: 174 tests, all pass. Runs under host load 5 had flaky xdist failures, which all passed alone and in full reruns. - **Python 3.15, before the pin (first push):** install.sh installed and ran Worthless 0.3.16 on 3.15.2 on macOS and in a bare `ubuntu:24.04` container with no compiler, where PyYAML fell back to pure Python. CI's "install.sh host matrix (distros, lock lifecycle, app container)" passed on that push too, including Alpine. The separate "service lock roundtrip (Linux Docker)" job failed on 3.15 (cffi has no 3.15 wheel; see How). For install.sh itself, the pin is about the source build, not about a failure. - **Docker install matrix:** the local run can't build images (OrbStack has no buildx). CI's install-docker workflow runs the full bare-distro matrix. - **Placement:** `check_changelog_placement.py` reports nothing under a shipped version. </details> 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## Summary by CodeRabbit * **Installer** * The installer now uses uv 0.13.7 and verifies its download with a SHA-256 checksum. Newly installed tools use Python 3.14.10 or later, but below Python 3.15; rerunning the installer may retain an existing Python version. * Update installers from a trusted network. The certificate checks do not cover the initial installer download. * **Security** * uv 0.13.7 rejects connections involving compromised eMudhra certificates. Behavior may differ on macOS or Windows when system certificates are enabled. * Older uv versions and system or overridden certificate stores may still trust compromised certificates, including intermediates. Certificate behavior varies by platform and by whether uv or pip uses system or bundled certificates. Configure the upstream certificate bundle with `WORTHLESS_UPSTREAM_CA_BUNDLE`. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
The eMudhra incident compromised intermediate CA keys that could be used to impersonate HTTPS sites.
Update rustls-webpki to 0.103.16, which rejects certificate chains containing the corresponding intermediate public keys.
Codex prepared this update.