From 6aae1ee425574224ed2fecc0a8a6f1290ff1b8f2 Mon Sep 17 00:00:00 2001 From: Garrett Allen <98648590+Gerrrt@users.noreply.github.com> Date: Wed, 7 Oct 2026 23:07:32 +0000 Subject: [PATCH] chore(sensitive): Immich's Postgres to 17-vectorchord1.1.1, from a build that had aged to 20 critical CVEs (#980) The pinned ghcr.io/immich-app/postgres:17-vectorchord0.4.3 was built on 2025-10-07, on Debian 12.11. Upstream never rebuilt that tag, and the weekly CVE scan found 20 critical and 119 high fixable findings in it. Dependabot offered nothing: it read 17-vectorchord0.4.3 and 17-vectorchord1.1.1 as unrelated tags. 17-vectorchord1.1.1 was built on 2026-10-06, on Debian 12.14. Scanned with the pinned trivy, it has 13 critical and 41 high. What remains is perl (three CVEs across four packages) and gosu's Go runtime, with no fixed upstream build yet, so #980 stays open for the scan to close. Postgres stays at 17. The extension moves from VectorChord 0.4.3 to 1.1.1, which is inside Immich v3.2.4's supported range (>=0.3 <2, server/src/constants.ts). At start, Immich runs ALTER EXTENSION vchord UPDATE TO the image's version, then reindexes the CLIP and face indexes. That path was run on throwaway containers under this block's exact hardening (user 999, read-only root, cap_drop ALL, the same tmpfs mounts, no network): - a 0.4.3 database with a vchordrq index and 500 rows; - restarted on 1.1.1; - ALTER EXTENSION to 1.1.1; - REINDEX, and an index-forced nearest-neighbour query returned 5 rows. The logs were clean. The live sensitive-immich-db was not touched. Refs #980 Co-Authored-By: Claude Opus 5.5 --- stacks/sensitive/compose.yaml | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/stacks/sensitive/compose.yaml b/stacks/sensitive/compose.yaml index 192b15b6..0446ace2 100644 --- a/stacks/sensitive/compose.yaml +++ b/stacks/sensitive/compose.yaml @@ -960,8 +960,19 @@ services: # November 2026, upstream states >= 14 and < 20 all work, and a library # born on a major that needs a dump-and-restore within months would be # choosing the migration on purpose. The tag carries the extension - # version, so Dependabot bumps both halves together. - image: ghcr.io/immich-app/postgres:17-vectorchord0.4.3@sha256:79b95b795f0911e95ffa4d092a2162c4d81a984d5629bc8f786afe0bc0657671 + # version, so the two move together. + # + # Dependabot does NOT move them (#980). It read 17-vectorchord0.4.3 and + # 17-vectorchord1.1.1 as unrelated tags, and offered nothing while the + # 0.4.3 build aged to 20 critical CVEs on Debian 12.11. 1.1.1, built + # 2026-10-06 on Debian 12.14, carried 13 (perl, and gosu's Go runtime, + # with no fixed build yet). So this pin is moved by hand when the weekly + # CVE scan's issue says so. Immich accepts VectorChord >=0.3 <2 + # (server/src/constants.ts), and at start it runs ALTER EXTENSION vchord + # UPDATE TO the image's version, then reindexes the CLIP and face indexes. + # That path was run on a throwaway copy of this block's hardening on + # 2026-10-07: 0.4.3 to 1.1.1, REINDEX, and an index scan answered. + image: ghcr.io/immich-app/postgres:17-vectorchord1.1.1@sha256:7f0b786ed5a7a9d26522dacbf46114a76e043a515ce5e020690fc6702e987b72 container_name: sensitive-immich-db # 2 GiB: upstream's stated floor for a Postgres under a container limit. mem_limit: 2048m