Repository navigation
Conversation
…ild 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 <noreply@anthropic.com>
There was a problem hiding this comment.
🟡 Changes recommended
The upgrade contradicts the linked issue’s recorded decision to wait without explicitly superseding it.
1 open finding
What changed in this PR
Updates Immich’s PostgreSQL image to reduce known critical and high-severity CVEs while retaining PostgreSQL 17.
Changes:
- Upgrades VectorChord from 0.4.3 to 1.1.1.
- Documents compatibility, testing, and manual update rationale.
| File | Description |
|---|---|
stacks/sensitive/compose.yaml |
Updates the database image pin and supporting rationale. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Gerrrt
enabled auto-merge (squash)
October 7, 2026 23:32
Owner
Author
This pull request was closed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Refs #980. That issue stays open after this merges. The weekly CVE scan shuts it on its own once the pinned digest scans clean, and this one does not yet. See below.
Why
ghcr.io/immich-app/postgres:17-vectorchord0.4.3was built on 2025-10-07, on Debian 12.11, and upstream has never rebuilt that tag. Its digest today is still the one pinned. Dependabot offered nothing, because it reads17-vectorchord0.4.3and17-vectorchord1.1.1as unrelated tags.Scanned with the repository's pinned trivy (0.75.0), HIGH/CRITICAL fixable findings only:
17-vectorchord0.4.3(was pinned)17-vectorchord0.5.317-vectorchord1.1.1(now pinned)What remains in 1.1.1: perl (three CVEs across
perl,perl-base,libperl5.36andperl-modules-5.36), and gosu's Go runtime (stdlib1.24.6). gosu is the entrypoint's privilege drop, used once at start. There is no fixed upstream build yet, so the issue stays open.What changes
stacks/sensitive/compose.yaml,immich-db: the image pin, and a comment recording why it moves by hand. Postgres stays at 17. Only the VectorChord extension moves, from 0.4.3 to 1.1.1. The hardening is unchanged.Immich handles the extension. v3.2.4 accepts VectorChord
>=0.3 <2(server/src/constants.ts). At start,database.repository.tsrunsALTER EXTENSION vchord UPDATE TOthe image's version, then reindexes the CLIP and face vector indexes.Tested
The upgrade was run on throwaway containers under this block's exact hardening: user 999, read-only root,
cap_drop: ALL,no-new-privileges, the same three tmpfs mounts, and--network none.CREATE EXTENSION vchord, 500 rows, and avchordrqcosine index.vchord1.1.1, with 0.4.3 installed.ALTER EXTENSION vchord UPDATE TO '1.1.1'.REINDEX, and an index-forced nearest-neighbour query returned 5 rows. The container logs were clean.The live
sensitive-immich-dbwas not touched, and it stayed healthy throughout. yamllint,check_image_pins.pyandcheck_docs.pypass.Deploy (operator, on trinity)
make backupset that includesimmich-dbfirst. It is the restore point if the extension upgrade misbehaves on the real library.make up STACK=sensitive. On first start, expect Immich's log to show the vchord update and a reindex of the CLIP and face indexes. On the real library this can take minutes.🤖 Generated with Claude Code