The security scan fails on uv.lock: certifi and pillow have advisories #827

What happens

The trivy CI job fails on uv.lock with 8 findings (2 CRITICAL, 6 HIGH). It is red on big-release itself, so it blocks every PR into it, including the 0.21.0 release PR (#784).

• certifi 2026.4.22: GHSA-6q48-6c7w-9gw2 (CRITICAL). It bundles the emSign root CAs, whose intermediate keys are compromised. Fixed in 2026.10.19.
• pillow 12.3.0: CVE-2026-112403 (CRITICAL), CVE-2026-112397, CVE-2026-112400, CVE-2026-112404, CVE-2026-112895, CVE-2026-112896, CVE-2026-112897 (HIGH). Fixed in 13.0.0. StemDeck does not import Pillow; it arrives through torchvision (audio-separator) and matplotlib (all-in-one-infer).

.trivyignore also carries entries for urllib3, anyio, fsspec and hydra-core that were deferred only because any uv.lock change sends every desktop install to a full download. Each says to drop it the next time the lock moves.

Who it affects

• Every contributor: no PR into big-release can go green.
• Source installs (./run.sh setup) and CI, which install from uv.lock.
• Desktop and Docker builds install from pyproject.toml at build time, so they likely already pick up the fixed versions, but CI does not test those.

What should happen

uv.lock resolves fixed versions of certifi and Pillow, and the deferred urllib3, anyio, fsspec and hydra-core ignores are removed because the fix is taken. The scan passes without new ignores for things that can be fixed.

Constraints

• Any uv.lock change changes the desktop runtimeId, so the in-app updater stops offering the release and every Windows and Linux desktop user does one full download. Accepted for 0.21.0.
• torch, torchvision and torchaudio must not move. packaging/torch-versions.json and a Rust drift test pin them to what the lock resolves.
• Pillow 13.0.0 requires Python 3.11 or later. The project still declares requires-python = ">=3.10", so the lock keeps a Pillow 12.3.0 entry for Python 3.10, and trivy reads every entry in the lock.