Repository navigation
security: distrust compromised eMudhra intermediates - #1
Merged
Merged
Conversation
Bump rustls-webpki to 0.103.16 and webpki-roots to 1.0.10 so certificate verification rejects the guessable eMudhra keys (CVE-2026-111943, RUSTSEC-2026-0382). Install Debian ca-certificates 20250419~deb12u2 in showdown image builders and pin CI Node.js to 22.23.4. Co-authored-by: Owen <battman21@users.noreply.github.com>
Move rustls to 0.23.46, the yanked chacha20 0.10.1 crate to 0.10.2, and showdown's quinn-proto to 0.11.19. These are compatible official releases for the remaining cargo audit findings. Co-authored-by: Owen <battman21@users.noreply.github.com>
Replace the exact Node and Debian CA pins with minimum floors, and replace Cargo exact pins with caret ranges. Update the workspace and campaign lockfiles to the latest compatible releases, including jsonwebtoken 11 and p256 0.14, and reject an untrusted TLS chain. Co-authored-by: Owen <battman21@users.noreply.github.com>
Raise live toolchains and images to the 22 Oct 2026 advisory baseline: rustc 1.99.1 with an MSRV floor of 1.96.1, Go 1.26.10 built with 1.27.3, Node 24.x with an engines floor, Python 3.14 with pip and certifi floors, Debian trixie campaign images, and cryptography >= 50.0.0. Clear the showdown hickory-resolver high and make the v33 image build the current replay source. Co-authored-by: Owen <battman21@users.noreply.github.com>
Advisory baseline coverageChecked every live component against the 22 Oct 2026 advisory baseline. Floors are minimums. The installed or resolved release is the current one where the lockfile or image could be updated. Commit
Scanners
Tests and smoke
|
battman21
marked this pull request as ready for review
October 22, 2026 10:17
setup-node was reusing the runner cache at 24.22.0, below the 24.22.1 floor. Ask setup-node and setup-python to resolve the latest release that matches the floating range. Co-authored-by: Owen <battman21@users.noreply.github.com>
rust-toolchain.toml named rustc 1.99.1 exactly. Use the stable channel and keep the CI check that rustc is at least 1.96.1. Co-authored-by: Owen <battman21@users.noreply.github.com>
Advisory baseline coverageUpdate for
The rest of the earlier coverage table is unchanged. CI for |
Advisory baseline coverageCI on |
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.
Summary
Removes the compromised eMudhra intermediates from the live trust path and brings every live component up to the 22 Oct 2026 advisory baseline. Requirements are floors (caret ranges,
>=, floating image tags, and the stable Rust channel) with build-time checks. Exact pins remain only in archived campaign evidence underresearch/showdown/evidence/.Certificate trust
rustls-webpki0.103.16,webpki-roots1.0.10,rustls0.23.46 (CVE-2026-111943 / RUSTSEC-2026-0382).chacha200.10.1 is 0.10.2. Showdownquinn-protois 0.11.19.Baseline floors
stable.rust-versionis 1.96.1. CI rejects a rustc older than 1.96.1.go 1.26.10withtoolchain go1.27.3. CI rejects an older toolchain and runsgovulncheck.scripts/check-node-floor.mjsaccept 22.23.4, 24.22.1, or 26.12.1. CI uses Node24.xwithcheck-latestso the runner cache cannot keep 24.22.0, plusengine-strictandnpm audit --audit-level=high.check-latest, requires 3.13.17 or newer, and upgradespip>=26.2.2andcertifi>=2026.10.19.cryptographymoved from==49.0.0to>=50.0.0.rust:1.99-trixieanddebian:trixie-slim, runapt-get upgrade, and fail the build unless rustc is at least 1.96.1 andca-certificatesis at least20250419+deb13u1. Each image curlshttps://example.comduring the build.replay_v01.rsand depends onlibcandtempfile, so the current source builds.hickory-resolver0.26.1 is 0.26.3.PHP, Java, Composer, Next.js, React,
python-jose, Starlette, Pillow, and PyJWT are not dependencies of this repository.Local verification
cargo test --workspace --locked --all-targets -- --include-ignoredpassed, including the Postgres graph test, the Supabase RLS test against PostgreSQL 16.15, and the untrusted-chain test.cargo clippy --workspace --all-targets --locked -- -D warnings,cargo fmt --all --check,cargo test --doc, andcargo build --workspace --locked --binspassed.go test ./...passed. Python 3.14.9 conformance passed (4 tests). Node 24.22.1npm testpassed (15 tests). The Node floor script also passed on 22.23.4.docker build --pull --no-cacheand smoked withcurl https://example.com.Scanner results and the component table are in the "Advisory baseline coverage" comments. CI on
f172cccis green:rustandconformanceboth passed with the stable Rust channel and the rustc >= 1.96.1 floor check. The pull request is ready for review and is not merged.