[BUG] The published guard-core-mcp image was built on 2026-10-21 and carries 14 advisories that master's lock already fixes #119

Value this delivers

A pull of ghcr.io/guard-core/guard-core-mcp:latest scans clean for fixable advisories.

What happened

The image ghcr.io/guard-core/guard-core-mcp:latest (sha256:f2164219b94f39e8bc48f94469fcf024031629aa95ee3d6fdf5451c65d352994, created 2026-10-21) has 14 distinct advisories with a fixed version in Trivy 0.74.0 (scan of 2026-11-02): 1 critical, 5 high, 4 medium and 4 low.

The critical one is GHSA-6q48-6c7w-9gw2 (certifi 2026.6.17, fixed in 2026.10.18). The rest are rustls 0.23.45 inside the uv and uvx binaries (4 each, fixed in 0.23.46), setuptools 70.3.0 (3), urllib3 2.7.0 (3), msgpack 1.1.2 (2) and opentelemetry-api 1.44.0 (1) in the app venv.

master's uv.lock already has certifi 2026.10.19, msgpack 1.2.3, opentelemetry-api 1.45.1 and urllib3 2.8.0. So the image is older than the lock, and no release or snapshot has rebuilt it since 2026-10-21. Dockerfile.hosted also copies uv 0.13.4 (COPY --from=ghcr.io/astral-sh/uv:0.13.4), and that is where the rustls findings come from. I didn't check which uv release bundles rustls 0.23.46 or newer. For setuptools, Trivy lists it under the Python target with no package path, and I didn't find where it comes from.

Steps to reproduce

1. Scan ghcr.io/guard-core/guard-core-mcp@sha256:f2164219b94f39e8bc48f94469fcf024031629aa95ee3d6fdf5451c65d352994 with Trivy 0.74.0 (vulnerability scanner only, fixed advisories only).
2. Compare with uv.lock on master.

Versions

Image digest above, Trivy 0.74.0 with DB ghcr.io/aquasecurity/trivy-db:2 on 2026-11-02, Debian 13.7 base (python:3.14-slim).

Additional context

The fix is a rebuild from master after the uv pin moves, and the setuptools source found. I would also tag the rebuild so the latest digest changes, since consumers pin by digest.