Finding 41 of bau-pm's v0.22.3 security review called this a pin to move.
It is not a pin: both bases here are floating tags, so what ships is
whatever the runner had cached. v0.1.0 went out with nginx 1.31.6 while
quay.io/nginx/nginx-unprivileged:alpine-slim had already moved to 1.31.8,
past five October CVEs - none of them reachable in a static file server
configured like this one, which is why --pull is the fix rather than a pin.
The CI build gets it too: a gate running against a months-old cached base
is not testing what the release builds.
A release is what applies this. The running image does not change until one
is cut.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
magdevandClaude Opus 5
d0a2feff20