Skip to content

fix(docker): refresh uv image for patched rustls-webpki (#51292) - #82084

Open
egilewski wants to merge 1 commit into
NousResearch:mainfrom
egilewski:codex/security-issue-51292
Open

fix(docker): refresh uv image for patched rustls-webpki (#51292)#82084
egilewski wants to merge 1 commit into
NousResearch:mainfrom
egilewski:codex/security-issue-51292

Conversation

@egilewski

@egilewski egilewski commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Refresh the pinned ghcr.io/astral-sh/uv source used by Docker from 0.11.6 to audited 0.11.33 Python 3.13 trixie digest, carrying rustls-webpki 0.103.13.
  • Add a deterministic regression test that binds the approved version/variant/digest and rejects the retired vulnerable digest.
  • Keep the uv/uvx paths, CLI flows, multi-architecture image family, and final runtime unchanged; the scope is Docker-shipped uv binaries only.

Validation

  • 83 Docker/packaging tests passed, plus implementation, security, and compatibility focused checks.
  • py_compile and diff checks passed.
  • Deep security and compatibility reviews found no remaining worthwhile comments.
  • Full Docker/Podman runtime and the canonical full suite were unavailable in this environment; the broader direct-run failures were missing-dependency environment failures.
  • CodeRabbit was unavailable after bounded seat-limit retries and was treated fail-open.

Fixes #51292

…#51292)

The production Dockerfile copied uv and uvx from uv 0.11.6, whose embedded
rustls-webpki 0.103.10 remained vulnerable even after Hermes application
dependency locks had moved to patched versions.

Pin the uv source stage to the audited 0.11.33 Python 3.13 trixie OCI index,
whose binaries carry rustls-webpki 0.103.13, and lock the version/variant to its
exact immutable digest in a deterministic regression contract. The same uv and
uvx paths, CLI flows, multi-architecture image family, and final runtime remain
unchanged. This is scoped to Docker-shipped uv binaries; host installers,
CI-only uv versions, and unrelated application dependency findings remain
outside the fix boundary.

Focused Docker and packaging validation passed (83 tests, plus the
implementation and compatibility adjacent checks), along with py_compile and
diff checks. The full canonical suite could not start because this pooled
checkout has no pytest virtualenv; the broader direct run's three failures were
environmental missing dotenv/mcp imports. CodeRabbit was unavailable after
both bounded seat-limit retries and was treated fail-open; the final deep
security and compatibility reviews are clean, including the repaired digest
binding regression.

Fixes NousResearch#51292
@alt-glitch alt-glitch added type/security Security vulnerability or hardening area/docker Docker image, Compose, packaging P2 Medium — degraded but workaround exists labels Aug 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/docker Docker image, Compose, packaging P2 Medium — degraded but workaround exists type/security Security vulnerability or hardening

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Container image v2026.6.19 contains fixable HIGH/CRITICAL CVEs blocking deployment

2 participants