Skip to content

Fixable CVEs in ghcr.io/immich-app/postgres (16 critical, 67 high) #980

Open

Description

@github-actions

The weekly CVE scan found fixable HIGH or CRITICAL vulnerabilities in ghcr.io/immich-app/postgres. This body is rewritten by every scan, and the issue closes itself when a scan finds the pinned digest clean.

The fix is normally the Dependabot bump for this image. If upstream has not released one, the fixed versions below say what to wait for.

ghcr.io/immich-app/postgres:17-vectorchord0.4.3

Stacks: sensitive. Digest: sha256:79b95b795f0911e95ffa4d092a2162c4d81a984d5629bc8f786afe0bc0657671.

Severity ID Package Installed Fixed in
CRITICAL CVE-2026-33845 libgnutls30 3.7.9-2+deb12u5 3.7.9-2+deb12u7
CRITICAL CVE-2026-42010 libgnutls30 3.7.9-2+deb12u5 3.7.9-2+deb12u7
CRITICAL CVE-2026-13221 libperl5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u4
CRITICAL CVE-2026-42496 libperl5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u4
CRITICAL CVE-2026-8376 libperl5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u4
CRITICAL CVE-2026-31789 libssl3 3.0.17-1~deb12u2 3.0.19-1~deb12u2
CRITICAL CVE-2026-31789 openssl 3.0.17-1~deb12u2 3.0.19-1~deb12u2
CRITICAL CVE-2026-13221 perl 5.36.0-7+deb12u2 5.36.0-7+deb12u4
CRITICAL CVE-2026-42496 perl 5.36.0-7+deb12u2 5.36.0-7+deb12u4
CRITICAL CVE-2026-8376 perl 5.36.0-7+deb12u2 5.36.0-7+deb12u4
CRITICAL CVE-2026-13221 perl-base 5.36.0-7+deb12u2 5.36.0-7+deb12u4
CRITICAL CVE-2026-42496 perl-base 5.36.0-7+deb12u2 5.36.0-7+deb12u4
CRITICAL CVE-2026-8376 perl-base 5.36.0-7+deb12u2 5.36.0-7+deb12u4
CRITICAL CVE-2026-13221 perl-modules-5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u4
CRITICAL CVE-2026-42496 perl-modules-5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u4
CRITICAL CVE-2026-8376 perl-modules-5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2026-109518 apt 2.6.1 2.6.2
HIGH CVE-2025-68973 dirmngr 2.2.40-1.1 2.2.40-1.1+deb12u2
HIGH CVE-2025-68973 gnupg 2.2.40-1.1 2.2.40-1.1+deb12u2
HIGH CVE-2025-68973 gnupg-l10n 2.2.40-1.1 2.2.40-1.1+deb12u2
HIGH CVE-2025-68973 gnupg-utils 2.2.40-1.1 2.2.40-1.1+deb12u2
HIGH CVE-2025-68973 gpg 2.2.40-1.1 2.2.40-1.1+deb12u2
HIGH CVE-2025-68973 gpg-agent 2.2.40-1.1 2.2.40-1.1+deb12u2
HIGH CVE-2025-68973 gpg-wks-client 2.2.40-1.1 2.2.40-1.1+deb12u2
HIGH CVE-2025-68973 gpg-wks-server 2.2.40-1.1 2.2.40-1.1+deb12u2
HIGH CVE-2025-68973 gpgconf 2.2.40-1.1 2.2.40-1.1+deb12u2
HIGH CVE-2025-68973 gpgsm 2.2.40-1.1 2.2.40-1.1+deb12u2
HIGH CVE-2025-68973 gpgv 2.2.40-1.1 2.2.40-1.1+deb12u2
HIGH CVE-2026-109518 libapt-pkg6.0 2.6.1 2.6.2
HIGH CVE-2026-4878 libcap2 1:2.66-4+deb12u1 1:2.66-4+deb12u3
HIGH CVE-2026-33846 libgnutls30 3.7.9-2+deb12u5 3.7.9-2+deb12u7
HIGH CVE-2026-3833 libgnutls30 3.7.9-2+deb12u5 3.7.9-2+deb12u7
HIGH CVE-2026-42009 libgnutls30 3.7.9-2+deb12u5 3.7.9-2+deb12u7
HIGH CVE-2026-40355 libgssapi-krb5-2 1.20.1-2+deb12u3 1.20.1-2+deb12u5
HIGH CVE-2026-40356 libgssapi-krb5-2 1.20.1-2+deb12u3 1.20.1-2+deb12u5
HIGH CVE-2026-40355 libk5crypto3 1.20.1-2+deb12u3 1.20.1-2+deb12u5
HIGH CVE-2026-40356 libk5crypto3 1.20.1-2+deb12u3 1.20.1-2+deb12u5
HIGH CVE-2026-40355 libkrb5-3 1.20.1-2+deb12u3 1.20.1-2+deb12u5
HIGH CVE-2026-40356 libkrb5-3 1.20.1-2+deb12u3 1.20.1-2+deb12u5
HIGH CVE-2026-40355 libkrb5support0 1.20.1-2+deb12u3 1.20.1-2+deb12u5
HIGH CVE-2026-40356 libkrb5support0 1.20.1-2+deb12u3 1.20.1-2+deb12u5
HIGH CVE-2026-103111 libpcre2-8-0 10.42-1 10.42-1+deb12u2
HIGH CVE-2026-86145 libpcre2-8-0 10.42-1 10.42-1+deb12u1
HIGH CVE-2026-89157 libpcre2-8-0 10.42-1 10.42-1+deb12u1
HIGH CVE-2026-89161 libpcre2-8-0 10.42-1 10.42-1+deb12u1
HIGH CVE-2023-31484 libperl5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u3
HIGH CVE-2026-42497 libperl5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2026-48962 libperl5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2026-57432 libperl5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2026-57433 libperl5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2025-6965 libsqlite3-0 3.40.1-2+deb12u1 3.40.1-2+deb12u2
HIGH CVE-2025-15467 libssl3 3.0.17-1~deb12u2 3.0.18-1~deb12u2
HIGH CVE-2025-69421 libssl3 3.0.17-1~deb12u2 3.0.18-1~deb12u2
HIGH CVE-2026-28387 libssl3 3.0.17-1~deb12u2 3.0.19-1~deb12u2
HIGH CVE-2026-28388 libssl3 3.0.17-1~deb12u2 3.0.19-1~deb12u2
HIGH CVE-2026-28389 libssl3 3.0.17-1~deb12u2 3.0.19-1~deb12u2
HIGH CVE-2026-28390 libssl3 3.0.17-1~deb12u2 3.0.19-1~deb12u2
HIGH CVE-2026-45447 libssl3 3.0.17-1~deb12u2 3.0.20-1~deb12u2
HIGH CVE-2026-84782 libssl3 3.0.17-1~deb12u2 3.0.22-1~deb12u2
HIGH CVE-2025-7424 libxslt1.1 1.1.35-1+deb12u1 1.1.35-1+deb12u2
HIGH CVE-2025-15467 openssl 3.0.17-1~deb12u2 3.0.18-1~deb12u2
HIGH CVE-2025-69421 openssl 3.0.17-1~deb12u2 3.0.18-1~deb12u2
HIGH CVE-2026-28387 openssl 3.0.17-1~deb12u2 3.0.19-1~deb12u2
HIGH CVE-2026-28388 openssl 3.0.17-1~deb12u2 3.0.19-1~deb12u2
HIGH CVE-2026-28389 openssl 3.0.17-1~deb12u2 3.0.19-1~deb12u2
HIGH CVE-2026-28390 openssl 3.0.17-1~deb12u2 3.0.19-1~deb12u2
HIGH CVE-2026-45447 openssl 3.0.17-1~deb12u2 3.0.20-1~deb12u2
HIGH CVE-2026-84782 openssl 3.0.17-1~deb12u2 3.0.22-1~deb12u2
HIGH CVE-2023-31484 perl 5.36.0-7+deb12u2 5.36.0-7+deb12u3
HIGH CVE-2026-42497 perl 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2026-48962 perl 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2026-57432 perl 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2026-57433 perl 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2023-31484 perl-base 5.36.0-7+deb12u2 5.36.0-7+deb12u3
HIGH CVE-2026-42497 perl-base 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2026-48962 perl-base 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2026-57432 perl-base 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2026-57433 perl-base 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2023-31484 perl-modules-5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u3
HIGH CVE-2026-42497 perl-modules-5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2026-48962 perl-modules-5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2026-57432 perl-modules-5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u4
HIGH CVE-2026-57433 perl-modules-5.36 5.36.0-7+deb12u2 5.36.0-7+deb12u4

Written by .github/workflows/cve-scan.yml in this run.

Activity

  1. added
    securityA credential, an exposure, or a control that is weaker than recorded
    sensitivestacks/sensitive on trinity (VLAN 99)
    on Oct 7, 2026
  2. Gerrrt commented on Oct 7, 2026

    @Gerrrt
    Owner

    Triage, 2026-10-07: wait for Immich to move past VectorChord 0.4.3

    Why there's no plain bump. ghcr.io/immich-app/postgres:17-vectorchord0.4.3 was built on 2025-10-07, and upstream has not rebuilt it since. The only way to newer packages is a newer VectorChord tag. Scanned with trivy 0.75.0 using cve-scan.yml's flags:

    Tag CRITICAL HIGH
    17-vectorchord0.4.3 (pinned) 20 119
    17-vectorchord0.5.3 17 63
    17-vectorchord1.1.1 13 41

    Immich would accept the newer tags. Immich 3.2.4's VECTORCHORD_VERSION_RANGE is >=0.3 <2. On start it runs ALTER EXTENSION vchord UPDATE and reindexes the CLIP and face vectors itself.

    Decided: wait. Immich's own docker-compose.yml, at v3.2.4, at v3.3.0-rc.2 and on main, still ships VectorChord 0.4.3. Moving the database that holds the photo library ahead of what upstream runs, for a partial reduction, isn't worth it. The database is reachable only from the Immich server inside the sensitive tier.

    Reopen this decision when:

    • Immich's compose moves past 0.4.3, at which point we follow it, with a backup first and time for the reindex;
    • or a finding appears here that is reachable from the network.

    🤖 Triage by Claude Code

  3. Gerrrt commented on Oct 7, 2026

    @Gerrrt
    Owner

    Still waiting, re-checked 2026-10-07 evening

    The trigger has not fired. Immich v3.3.0 shipped at 18:37 UTC today. Its docker/docker-compose.yml still pins ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0, as v3.2.4 and main do. So the decision above stands.

    #1061 moved the pin to 17-vectorchord1.1.1 ahead of upstream. It was opened without this triage in view, and it is closed unmerged in favour of it.

    Ready for when the trigger fires. #1061 ran the upgrade path on throwaway containers under immich-db's exact hardening:

    • user 999, read-only root, cap_drop: ALL, no-new-privileges;
    • the same three tmpfs mounts;
    • --network none.

    The steps:

    1. A 0.4.3 database with a vchordrq cosine index and 500 rows.
    2. Restarted on 17-vectorchord1.1.1@sha256:7f0b786ed5a7a9d26522dacbf46114a76e043a515ce5e020690fc6702e987b72, with the same volume.
    3. ALTER EXTENSION vchord UPDATE TO '1.1.1', which is Immich's own startup step.
    4. REINDEX, after which an index-forced nearest-neighbour query returned 5 rows. The logs were clean.

    When Immich's compose moves past 0.4.3, the move is the pin plus the comment from #1061's diff. Take a make backup set with immich-db first, and allow time for the reindex of the real CLIP and face indexes.

    🤖 Triage by Claude Code

  4. changed the title [-]Fixable CVEs in ghcr.io/immich-app/postgres (20 critical, 119 high)[/-] [+]Fixable CVEs in ghcr.io/immich-app/postgres (20 critical, 122 high)[/+] on Oct 10, 2026
  5. github-actions commented on Oct 10, 2026

    @github-actions
    Author

    New since the last scan: CVE-2026-78667, CVE-2026-78669, CVE-2026-97031.

  6. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    Still waiting, re-checked 2026-10-10

    The trigger has not fired. Immich v3.3.1 shipped on 2026-10-08. Its docker/docker-compose.yml still pins ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0, and so does main.

    There is no digest bump either. Upstream has not rebuilt 17-vectorchord0.4.3. The tag still resolves to sha256:79b95b795f0911e95ffa4d092a2162c4d81a984d5629bc8f786afe0bc0657671, which is the digest we pin.

    Nothing has changed in reachability. immich-db is still reachable only from the Immich server inside the sensitive tier. The decision and the triggers for revisiting it stand as written above, and the upgrade path #1061 tested is ready when they fire.

    🤖 Triage by Claude Code

  7. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    This is waiting on upstream. Nothing in the repo needs to change.

    • The pinned digest is current: ghcr.io/immich-app/postgres:17-vectorchord0.4.3 (sha256:79b95b79…). pin-digests.sh reports no drift, so the tag hasn't been rebuilt since it was pinned.
    • There is no newer release on the registry to move to.
    • The fixed versions exist (table above), but no published image includes them yet. Mostly:
      • stdlib: 59 findings, fixed in 27 different versions (see the table)
      • libperl5.36: 8 findings, fixed in 2 different versions (see the table)
      • libssl3: 8 findings, fixed in 3 different versions (see the table)
      • openssl: 8 findings, fixed in 3 different versions (see the table)
      • perl: 8 findings, fixed in 2 different versions (see the table)
      • perl-base: 8 findings, fixed in 2 different versions (see the table)
      • and 43 more across 25 other packages

    When upstream rebuilds or ships a release with these fixes, Dependabot should open the bump. Check it with trivy and check_image_pins.py, then deploy. The next scan will then close this issue.

  8. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    The criticals, traced against the live database, 2026-10-10

    This is the same trace as on #978, #979, #1002 and the others. I checked it against the running sensitive-immich-db on trinity (postgres:17-vectorchord0.4.3@sha256:79b95b79…); a fresh trivy 0.75.0 scan agrees. The 20 critical rows are 10 CVEs, and none is reachable. The Postgres settings below were read with psql inside the container (SHOW ssl, pg_hba_file_rules, pg_extension, pg_language).

    CVE Package What the bug needs What the live database does Reachable?
    CVE-2026-33845 libgnutls30 3.7.9 GnuTLS handling a DTLS handshake GnuTLS is mapped into every postgres process, but only as a dependency of libldap-2.5 (ldd: libldap-2.5.so.0 -> gnutls). Postgres does its own TLS with OpenSSL. libldap would use GnuTLS only as an LDAP client, and only for ldap auth. pg_hba has no ldap rules: trust on the local socket, 127.0.0.1 and ::1, and scram-sha-256 for everything else. Nothing speaks DTLS. No
    CVE-2026-42010 libgnutls30 3.7.9 A GnuTLS server configured for RSA-PSK GnuTLS is never a server here. It's an unused LDAP client library. No
    CVE-2026-31789 libssl3/openssl 3.0.17 32-bit OpenSSL hex-printing a huge SKID/AKID SHOW ssl is off, so Postgres negotiates no TLS at all, and the container is x86_64. No
    CVE-2026-13221, CVE-2026-8376 perl, libperl5.36, perl-modules Perl compiling an attacker-controlled regex (8376 also needs 32-bit) Perl never runs. The processes are docker-init → immich-docker-entrypoint.sh, then the postmaster and its background workers. No PL/Perl: pg_language is c, internal, plpgsql, sql, and no plperl*.so is installed. No
    CVE-2026-42496 perl-modules-5.36 (Archive::Tar) Archive::Tar extracting a hostile tarball Archive/Tar.pm is present here, unlike in linkding and ML, but nothing invokes Perl. No
    CVE-2023-24538, CVE-2023-24540, CVE-2024-24790, CVE-2025-68121 Go stdlib 1.18.2 in /usr/local/bin/gosu html/template rendering, net/netip, or crypto/tls session resumption gosu is the entrypoint's privilege drop, used only when it starts as root. The container runs as uid 999 (postgres), so it's never called. Even when run, it does none of those things: it setuids and execs. No

    Extensions in use are vchord 0.4.3, vector 0.8.1, cube, earthdistance, pg_trgm, unaccent, uuid-ossp and plpgsql, with shared_preload_libraries = vchord.so. None is implicated by any of the ten.

    This confirms the wait decided above, now with a trace behind it. The DB's network clients must pass scram-sha-256, and the only one is immich-server inside the sensitive tier. The HIGHs aren't covered by this trace. The upgrade path #1061 tested (VectorChord 1.1.1, 13C/41H) stays parked until Immich's own compose moves.

    What would change this:

    • Turning on ssl, LDAP auth in pg_hba, or plperl.
    • Running the container as root, which brings gosu into play, though gosu still does none of the vulnerable things.

    To reproduce:

    docker exec sensitive-immich-db sh -c 'uname -m; id; cat /proc/[0-9]*/maps | grep -oE "/[^ ]*(gnutls|libperl)[^ ]*" | sort -u; ldd /lib/x86_64-linux-gnu/libldap-2.5.so.0 | grep gnutls; psql -U postgres -d immich -Atc "SHOW ssl;" -c "SELECT type,auth_method FROM pg_hba_file_rules;" -c "SELECT lanname FROM pg_language;"'

    🤖 Traced by Claude Code

  9. changed the title [-]Fixable CVEs in ghcr.io/immich-app/postgres (20 critical, 122 high)[/-] [+]Fixable CVEs in ghcr.io/immich-app/postgres (16 critical, 67 high)[/+] on Oct 12, 2026
  10. changed the title [-]Fixable CVEs in ghcr.io/immich-app/postgres (16 critical, 67 high)[/-] [+]Fixable CVEs in ghcr.io/immich-app/postgres (16 critical, 69 high)[/+] on Oct 26, 2026
  11. github-actions commented on Oct 26, 2026

    @github-actions
    Author

    New since the last scan: CVE-2026-84782.

  12. changed the title [-]Fixable CVEs in ghcr.io/immich-app/postgres (16 critical, 69 high)[/-] [+]Fixable CVEs in ghcr.io/immich-app/postgres (16 critical, 71 high)[/+] on Nov 9, 2026
  13. github-actions commented on Nov 9, 2026

    @github-actions
    Author

    New since the last scan: CVE-2026-109518.

  14. Gerrrt commented on Nov 9, 2026

    @Gerrrt
    Owner

    Still waiting, re-checked 2026-11-09

    Trigger 1 has not fired. Immich's docker/docker-compose.yml still pins ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0 at v3.3.6 (Latest, the version we run), at v3.4.0-rc.3 and on main. VECTORCHORD_VERSION_RANGE is still >=0.3 <2.

    There is no rebuild either. 17-vectorchord0.4.3 still resolves to sha256:79b95b795f0911e95ffa4d092a2162c4d81a984d5629bc8f786afe0bc0657671, which is the digest we pin. So Dependabot has no bump to open.

    Trigger 2 has not fired. The scan has added two CVEs since the 2026-10-10 trace, both HIGH. I checked them against the running sensitive-immich-db, and neither is reachable:

    CVE Package What the bug needs What the live database does Reachable?
    CVE-2026-84782 libssl3/openssl 3.0.17 An OpenSSL DTLS handshake with message retransmission (out-of-bounds read) Postgres speaks TLS over TCP, never DTLS, and SHOW ssl is still off, so no TLS is negotiated at all. No
    CVE-2026-109518 apt, libapt-pkg6.0 2.6.1 An apt run fetching packages over a connection an on-path attacker can tamper with apt never runs. The container is uid 999 on a read-only root (ReadonlyRootfs=true), and its processes are docker-init → immich-docker-entrypoint.sh, the postmaster and its background workers. No

    The rest is unchanged. pg_hba auth methods are still trust (local) and scram-sha-256, and the image is x86_64.

    The decision and its triggers stand. The #1061 upgrade path (VectorChord 1.1.1) stays parked until Immich's own compose moves. When it does, take a make backup set with immich-db first and allow time for the reindex.

    🤖 Triage by Claude Code

  15. changed the title [-]Fixable CVEs in ghcr.io/immich-app/postgres (16 critical, 71 high)[/-] [+]Fixable CVEs in ghcr.io/immich-app/postgres (16 critical, 67 high)[/+] on Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    securityA credential, an exposure, or a control that is weaker than recordedsensitivestacks/sensitive on trinity (VLAN 99)

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions