Repository navigation
Open
Labels
securityA credential, an exposure, or a control that is weaker than recordedA credential, an exposure, or a control that is weaker than recordedsensitivestacks/sensitive on trinity (VLAN 99)stacks/sensitive on trinity (VLAN 99)
Description
The weekly CVE scan found fixable HIGH or CRITICAL vulnerabilities in ghcr.io/immich-app/immich-server. 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/immich-server:v3.4.1
Stacks: sensitive. Digest: sha256:7c489add298fc2f92cda4c777de6462aa206877e04087b815f62c7664af0b53b.
| Severity | ID | Package | Installed | Fixed in |
|---|---|---|---|---|
| CRITICAL | CVE-2026-42216 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| CRITICAL | CVE-2026-42217 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| HIGH | CVE-2026-109518 | apt | 3.0.3 | 3.0.4 |
| HIGH | CVE-2026-102276 | brace-expansion | 5.0.9 | 5.0.10, 3.0.7, 2.1.5, 1.1.19 |
| HIGH | CVE-2026-102278 | brace-expansion | 5.0.9 | 5.0.11, 3.0.8, 2.1.6, 1.1.20 |
| HIGH | CVE-2026-18446 | fast-uri | 3.1.4 | 2.4.4, 3.1.5, 4.1.2 |
| HIGH | CVE-2026-75899 | fast-uri | 3.1.4 | 2.4.5, 3.1.6, 4.1.3 |
| HIGH | CVE-2026-75931 | fast-uri | 3.1.4 | 2.4.5, 3.1.6, 4.1.3 |
| HIGH | CVE-2026-75975 | fast-uri | 3.1.4 | 2.4.5, 3.1.6, 4.1.3 |
| HIGH | CVE-2026-76172 | fast-uri | 3.1.4 | 2.4.5, 3.1.6, 4.1.3 |
| HIGH | CVE-2026-84292 | fast-uri | 3.1.4 | 2.4.6, 3.1.7, 4.1.4 |
| HIGH | CVE-2026-63209 | github.com/klauspost/compress | v1.18.6 | 1.18.7 |
| HIGH | CVE-2026-56854 | golang.org/x/crypto | v0.52.0 | 0.55.0 |
| HIGH | CVE-2026-46600 | golang.org/x/net | v0.55.0 | 0.56.0 |
| HIGH | CVE-2026-78661 | golang.org/x/net | v0.55.0 | 0.62.0 |
| HIGH | CVE-2026-78669 | golang.org/x/net | v0.55.0 | 0.60.0 |
| HIGH | CVE-2026-56851 | golang.org/x/text | v0.37.0 | 0.41.0 |
| HIGH | CVE-2026-56852 | golang.org/x/text | v0.37.0 | 0.39.0 |
| HIGH | CVE-2026-84304 | google.golang.org/grpc | v1.81.1 | 1.83.1 |
| HIGH | CVE-2026-84445 | google.golang.org/grpc | v1.81.1 | 1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e |
| HIGH | GHSA-hrxh-6v49-42gf | google.golang.org/grpc | v1.81.1 | 1.82.1 |
| HIGH | CVE-2026-109518 | libapt-pkg7.0 | 3.0.3 | 3.0.4 |
| HIGH | CVE-2026-27622 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| HIGH | CVE-2026-34379 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| HIGH | CVE-2026-34543 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| HIGH | CVE-2026-34544 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| HIGH | CVE-2026-34588 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| HIGH | CVE-2026-40244 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| HIGH | CVE-2026-40250 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| HIGH | CVE-2026-41142 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| HIGH | CVE-2026-59184 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| HIGH | CVE-2026-59186 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| HIGH | CVE-2026-59189 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| HIGH | CVE-2026-59981 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| HIGH | CVE-2026-59982 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| HIGH | CVE-2026-68515 | libopenexr-3-1-30 | 3.1.13-2 | 3.2.12-1~deb13u1 |
| HIGH | CVE-2026-113872 | multer | 2.4.0 | 2.5.0 |
| HIGH | CVE-2026-116304 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116306 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116307 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116309 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116314 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116315 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116316 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116317 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116319 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116320 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116323 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116325 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116326 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116328 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116330 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116331 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116332 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116335 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116336 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120139 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120141 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120142 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120143 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120145 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120147 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120148 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120149 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120150 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120151 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120153 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-14661 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-18447 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-6460 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-6467 | postgresql-client-17 | 17.11-1.pgdg13+2 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116576 | systeminformation | 5.33.15 | 5.33.16 |
| HIGH | CVE-2026-109383 | undici | 6.28.0 | 6.29.1, 7.30.1, 8.12.2 |
| HIGH | CVE-2026-109383 | undici | 8.11.2 | 6.29.1, 7.30.1, 8.12.2 |
| HIGH | CVE-2026-109829 | undici | 8.11.2 | 7.30.1, 8.12.2 |
| HIGH | CVE-2026-109869 | undici | 6.28.0 | 6.29.1, 7.30.1, 8.12.2 |
| HIGH | CVE-2026-109869 | undici | 8.11.2 | 6.29.1, 7.30.1, 8.12.2 |
| HIGH | CVE-2026-19534 | undici | 6.28.0 | 6.28.1, 7.29.1, 8.10.2 |
| HIGH | CVE-2026-87018 | undici | 6.28.0 | 6.29.1, 7.30.1, 8.12.2 |
| HIGH | CVE-2026-87018 | undici | 8.11.2 | 6.29.1, 7.30.1, 8.12.2 |
| HIGH | CVE-2026-76844 | zlib1g | 1:1.3.dfsg+really1.3.1-1+b1 | 1:1.3.dfsg+really1.3.1-1+deb13u1 |
| HIGH | CVE-2026-85091 | zlib1g | 1:1.3.dfsg+really1.3.1-1+b1 | 1:1.3.dfsg+really1.3.1-1+deb13u1 |
Written by .github/workflows/cve-scan.yml in this run.
Metadata
Metadata
Assignees
Labels
securityA credential, an exposure, or a control that is weaker than recordedA credential, an exposure, or a control that is weaker than recordedsensitivestacks/sensitive on trinity (VLAN 99)stacks/sensitive on trinity (VLAN 99)
Activity
[-]Fixable CVEs in ghcr.io/immich-app/immich-server (2 critical, 50 high)[/-][+]Fixable CVEs in ghcr.io/immich-app/immich-server (4 critical, 48 high)[/+]github-actions commentedon Oct 10, 2026
New since the last scan: CVE-2026-106445, CVE-2026-106446.
chore(sensitive): Immich v3.2.4 -> v3.3.1, ahead of Sunday's Dependab…
Gerrrt commentedon Oct 10, 2026
Triage, 2026-10-10: the bump we could take has merged but isn't deployed. What's left waits on Immich.
v3.2.4, scanned before #1129 merged today and moved the pin tov3.3.1@sha256:db996e35…. trinity hasn't been redeployed yet:sensitive-immich-serverand-machine-learningare still running v3.2.4 (docker ps, 2026-10-10).--severity HIGH,CRITICAL --ignore-unfixed) and got 4 critical and 34 high, against 4 and 48 for v3.2.4. That matches chore(sensitive): Immich v3.2.4 -> v3.3.1, ahead of Sunday's Dependabot (#979) #1129's numbers. Debian's gzip, sqlite and openssl, plus npm's compression, multer and sharp, are fixed.main'spnpm-lock.yamlstill pins all three at those versions, so the next release won't fix them unless someone bumps them first.immich.matrix.elysium. I didn't trace which of these packages sit on a request path, so I'm not claiming any are unreachable.Next steps:
make upon the sensitive stack, thenmake check-container-health). Sunday's scan then reads v3.3.1 and this body drops to 4 / 34.Revisit this when: an Immich release's lockfile moves those three packages, or one of these findings turns out to be reachable through Caddy.
Gerrrt commentedon Oct 10, 2026
Deployed, 2026-10-10: trinity now runs Immich v3.3.1 (#1129). This is step 1 of the triage above.
make up STACK=sensitivefrommainata79e3e2. All 20 healthchecks pass, and the 13 single-file config mounts match the repo.sensitive-immich-serverandsensitive-immich-machine-learningare both onv3.3.1. The server log shows four migrations succeeded, thenImmich Server is listening … [v3.3.1].https://immich.matrix.elysium/api/server/versionreturns3.3.1, and the UI returns 200.The next weekly scan should rewrite this body to v3.3.1's 4 critical and 34 high. The issue stays open for step 2: an Immich release that bumps handlebars, proxy-addr and tar.
Gerrrt commentedon Oct 10, 2026
Deployed and verified on trinity, 2026-10-10
#1129 (squash
1c628f3) moved immich-server and immich-machine-learning to v3.3.1. Both were running on trinity by 14:36 UTC.What was checked:
PersonSharing. It then printedImmich Server is listening … [v3.3.1].make check-container-health STACK=sensitivepassed: 20 of 20 healthy. The ML container sits behind themlprofile, so that check skips it. Docker reports ithealthy, and it answerspongto the server onimmich-machine-learning:3003./predicta text query usingViT-B-32__openai. It got back a 512-dimension CLIP embedding.smart_search. It ran throughclip_index(VectorChord 0.4.3, unchanged) and returned ranked matches from the 601 embedded assets.This issue stays open. v3.3.1 cuts the server's fixable findings from 4 critical / 48 high to 4 / 34. What remains are transitive npm dependencies inside upstream's build. The weekly scan closes this once a pinned digest scans clean.
🤖 Posted by Claude Code
Gerrrt commentedon Oct 10, 2026
Deployed:
immich-serverv3.3.1 is running on trinity (2026-10-10, ~14:36Z), via #1129 (squash 1c628f3).ghcr.io/immich-app/immich-server:v3.3.1@sha256:db996e352359771c6a3db121a0ed8761516b22f727fc092a0f46dcfef82c1bc1.immich-machine-learningmoved to v3.3.1 with it so the versions match. Its CVEs are tracked on Fixable CVEs in ghcr.io/immich-app/immich-machine-learning (2 critical, 18 high) #978./api/server/versionreturns 3.3.1, andmake check-container-health STACK=sensitivepasses for all 20 of 20 services.immich-db: unchanged on17-vectorchord0.4.3. Upstream's compose still pins VectorChord 0.4.3, so Fixable CVEs in ghcr.io/immich-app/postgres (16 critical, 67 high) #980's trigger has not fired.Why this issue stays open. Scanned with the pinned trivy,
--ignore-unfixed, HIGH/CRITICAL, on 2026-10-10:Next step: take the next Dependabot bump. The weekly scan closes this issue itself once the deployed digest scans clean.
Gerrrt commentedon Oct 10, 2026
The four criticals, traced through Caddy, 2026-10-10
This closes the gap the triage above left open: "I didn't trace which of these packages sit on a request path." I traced each one against the deployed
immich-server:v3.3.1@sha256:db996e35…, using trivy 0.75.0's PkgPath and each advisory's precondition, then reading the image's ownserver/distandnode_modules/.pnpm. None of the four is reachable as deployed.allowProtoMethodsByDefaultenabledservices/storage-template.service.js. It compiles with{ knownHelpers: undefined, strict: true }and renderstemplate(substitutions)with no runtime options, so the prototype-method access the bug needs is never turned on. The template is the admin-only storage template:PUT /api/system-configrequiresadmin: trueplusSystemConfigUpdate.compile()instead of a stringcompile()input isstorageTemplate.template, which the config schema validates asz.string()(dtos/config.dto.js:283). An object is rejected before it reaches handlebars, and only an admin can set it.::ffff:10.0.0.0/8app.set('trust proxy', ['loopback', ...IMMICH_TRUSTED_PROXIES]). We setIMMICH_TRUSTED_PROXIES: 172.28.99.2, Caddy's fixed address, as a plain IPv4 (stacks/sensitive/compose.yaml:880). Neither entry is the misparsed form.::ffff:notationtar@7isnode-gyp@13.0.0, the native-addon build tool. Nothing inserver/distimportstar.What would change this:
z.string()config fields that handlebars doesn't render.IMMICH_TRUSTED_PROXIESchanges to an IPv6-mapped CIDR.tarat runtime, for example backup restore.Each would show up in the image's
dist/or in our compose diff. The remaining 34 HIGHs aren't covered by this trace.To reproduce:
🤖 Traced by Claude Code
[-]Fixable CVEs in ghcr.io/immich-app/immich-server (4 critical, 48 high)[/-][+]Fixable CVEs in ghcr.io/immich-app/immich-server (4 critical, 34 high)[/+]github-actions commentedon Oct 10, 2026
New since the last scan: CVE-2026-90776.
Gerrrt commentedon Oct 10, 2026
The HIGHs, traced against the live server, 2026-10-10: three are reachable before login
This follows the criticals trace above, against the running
sensitive-immich-serveron trinity (v3.3.1@sha256:db996e35…). The 34 rows are 26 distinct (CVE, package) pairs. For each one I mapped runtime dependents in the image's pnpm store, then checkedserver/distand the live config. Three are reachable before authentication, from any device on Hicks: denial of service only, with no data access. The rest aren't reachable.Reachable: the WebSocket stack (socket.io → engine.io → ws)
Immich's gateway is
@WebSocketGateway({ path: '/api/socket.io', transports: ['websocket'], cors: true }). Caddy passesimmich.matrix.elysiumstraight toimmich-server:2283, WebSocket upgrades included. Caddy publishes0.0.0.0:443on trinity, anddocs/network.mdpassesvlan50 → 10.0.99.40:443, by segment rather than host, so any device on Hicks can open/api/socket.io. Immich's auth runs inhandleConnection, after the transport and parser have already run. On failure it callsclient.disconnect(), which in socket.io defaults toclose = false: it leaves the namespace but doesn't close the engine.io connection.maxPayload, until the process is OOM-killedwsparses frames before anything else runs. No session or auth is involved.EIOand a crafted heartbeat can throw an uncaught exception, which crashes the processtransports: ['websocket']: a second WebSocket request carrying an existingsidgoesonWebSocket → createTransport → client._maybeUpgrade, gated only byupgrading/upgraded, which a directly opened WebSocket session has neither of.verify()skips the transport check for upgrades. Thesidcomes from the attacker's own unauthenticated handshake. (This is from reading engine.io 6.6.8'sserver.js/socket.jsin the image. I didn't exercise it, and won't against the live service.)Impact: Immich's API process (
immich-api) dies or is OOM-killed. The container runsrestart: unless-stoppedunder amem_limitof 3 GiB. An OOM kill of the container restarts it. I haven't tested whether a crash of just theimmich-apichild is respawned by the parentimmichprocess or takes the container down. In-flight uploads and jobs are interrupted, and a repeated attack keeps it down. Nothing is read or written.Upstream: Immich
main'spnpm-lock.yaml(last changed 2026-10-07) still pinsengine.io@6.6.8,socket.io-parser@4.2.6andws@8.20.1, so the next release won't fix these unless they're bumped first. The fixes are engine.io 6.6.10, socket.io-parser 4.2.7 and ws 8.21.0.Not reachable
ajv ← conf ← react-email, the email-preview CLI. It isn't loaded bydist/.minimatch ← glob/readdir-glob ← archiverandreact-email. Downloads usearchiver('zip')with appended files, neverarchive.glob. The external-library crawler usesfast-glob(micromatch/braces, not brace-expansion), with exclusion patterns that only the admin sets. The/usr/local/libcopies belong to global npm.utils/config.jsreadsIMMICH_CONFIG_FILE, which isn't set. The other dependents are swagger and nest-commander (CLI).email.repository.js. SMTP isn't configured:system-confighas nonotifications.smtp.enabled, so it defaults to false (read-only query onimmich-db).getAuthContext, and noIMMICH_TELEMETRY_*/OTEL_*is set.node-gyp(bcrypt/sharp install time), plus global npm's copies.immichandimmich-api, through glib (libglib/libgio/libgobject) under libvips. The CVE needs an attacker-controlled regex through PCRE2's JIT API, and glib'sGRegexpatterns come from library code, not image data.Options (for the decision, not taken)
/api/socket.io. The web UI and the mobile app need it for live updates, so it can't be blocked outright.To reproduce:
🤖 Traced by Claude Code
Gerrrt commentedon Oct 11, 2026
Option 2 taken, 2026-10-11: noted on Immich's open Renovate PR immich-app/immich#32128 (comment) that its lockfile still resolves engine.io 6.6.8 / socket.io-parser 4.2.6 although socket.io 4.8.4's ranges allow the patched 6.6.10 / 4.2.7 (which also brings ws 8.21). It's a public dependency-hygiene note with no exploit detail. It isn't a security report, since Immich's SECURITY.md wants a tested reproduction for those. When the Immich release that carries those versions lands, scan it before bumping, then the weekly scan closes this. Options 1 (accept meanwhile) and 3 (Caddy limits on /api/socket.io) still stand.
Gerrrt commentedon Oct 11, 2026
Option 3 (limits at Caddy) checked, 2026-10-11: not available, and it wouldn't help.
caddy:2.11.7@sha256:f2a1290d…, and trinity'ssensitive-caddyruns that digest.caddy list-modulesshows 135 standard modules and no rate or connection limiter. The only match for "limit"/"conn" ishttp.reverse_proxy.selection_policies.least_conn, a load-balancing policy. A limiter would need the third-partycaddy-ratelimitmodule in a custom build, and this repository builds no images./api/socket.io: the ws fragment flood and the socket.io-parser attachment count work within a single connection, and the engine.io upgrade needs one handshake plus one upgrade. A per-client rate or connection limit still admits that connection. Blocking/api/socket.iooutright would break live updates in the web UI and the mobile app.That leaves option 1 (accept: household-only, DoS-only, auto-restart) while option 2 (the note on immich-app/immich#32128) waits for an Immich release that resolves engine.io ≥ 6.6.10, socket.io-parser ≥ 4.2.7 and ws ≥ 8.21.0. Scan that release before bumping. Nothing in the repo changes.
[-]Fixable CVEs in ghcr.io/immich-app/immich-server (4 critical, 34 high)[/-][+]Fixable CVEs in ghcr.io/immich-app/immich-server (4 critical, 46 high)[/+]github-actions commentedon Oct 19, 2026
New since the last scan: CVE-2026-66046, CVE-2026-76956, CVE-2026-76957, CVE-2026-77214, CVE-2026-8286, CVE-2026-8927, CVE-2026-92392, CVE-2026-93990, CVE-2026-96889.
[-]Fixable CVEs in ghcr.io/immich-app/immich-server (4 critical, 46 high)[/-][+]Fixable CVEs in ghcr.io/immich-app/immich-server (4 critical, 52 high)[/+]github-actions commentedon Oct 26, 2026
New since the last scan: CVE-2023-54404, CVE-2026-109869, CVE-2026-111181, CVE-2026-111497, CVE-2026-113872.
[-]Fixable CVEs in ghcr.io/immich-app/immich-server (4 critical, 52 high)[/-][+]Fixable CVEs in ghcr.io/immich-app/immich-server (5 critical, 55 high)[/+]github-actions commentedon Nov 2, 2026
New since the last scan: CVE-2026-109383, CVE-2026-116576, CVE-2026-87018.
[-]Fixable CVEs in ghcr.io/immich-app/immich-server (5 critical, 55 high)[/-][+]Fixable CVEs in ghcr.io/immich-app/immich-server (5 critical, 40 high)[/+]github-actions commentedon Nov 9, 2026
New since the last scan: CVE-2026-109518, CVE-2026-76844, CVE-2026-85091.
Gerrrt commentedon Nov 9, 2026
v3.3.6 triage, 2026-11-09: one more DoS before login. v3.4.0 fixes them all.
Where things stand. trinity runs
immich-server:v3.3.6@sha256:e1981983…(#1321), and it's Immich's latest stable release. There's no bump to take yet. The three WebSocket DoS rows from the 2026-10-10 trace (ws, socket.io-parser, engine.io) are still present and still reachable in v3.3.6.What's new since the v3.3.1 trace
I traced these against the running container, by reading code and process maps only. Nothing was sent to the service.
workers/api.jscallsNestFactory.create(ApiModule, …)with Nest's defaultbodyParser, which mounts express's json/urlencoded parsers globally, before any guard. body-parser'scontentstream()pipes aContent-Encoding: gzipbody intozlib.createGunzip(). Caddy'simmich.matrix.elysiumblock is a barereverse_proxy.FileUploadInterceptor, andFileInterceptoron backup upload), and those run after the auth guard. Backup upload is admin-only. There are 0 shared links, so no anonymous upload path exists.fdir's dev dependency. Nothing inserver/distimports it./usr/local/lib/node_modules/npm. Immich's own copy (6.26.0, already in the earlier trace) sits undernode-gyp.immichandimmich-apithrough libvips (libjxl, freetype). Node's own gzip and brotli are bundled, so they don't use it. Attacker input reaches it only as uploaded media, which needs a login.Impact, now known. When
immich-apicrashes, the parentimmichprocess'sonExitcallsprocess.exit(exitCode). That stops the container, along with the microservices worker and any running jobs.restart: unless-stoppedbrings it back (restart count 0 so far). This answers the question the 2026-10-10 trace left open. Repeating the request keeps Immich down. Nothing is read or written.Upstream has fixed all of these in v3.4.0
pnpm-lock.yamlatv3.4.0-rc.3(2026-11-06), and onmain, resolves:ws 8.20.1 stays in the lockfile, but only under
engine.io-client, which isn't on the server path. The Debian rows depend on v3.4.0's base image.Decision: wait for v3.4.0. No Caddy stopgap. A 415 matcher like #1343's was considered, but v3.4.0 stable looks days away.
Next step: when the v3.4.0 Dependabot PR comes:
Refs #979in the PR body.make up STACK=sensitive.The weekly scan then closes this issue, or lists what's left.
Revisit if v3.4.0 slips well past rc.3, or its stable lockfile differs from rc.3's. In either case, the #1343-style Caddy matcher becomes worth doing.
To reproduce:
🤖 Traced by Claude Code
[-]Fixable CVEs in ghcr.io/immich-app/immich-server (5 critical, 40 high)[/-][+]Fixable CVEs in ghcr.io/immich-app/immich-server (2 critical, 80 high)[/+]github-actions commentedon Nov 16, 2026
New since the last scan: CVE-2026-109829, CVE-2026-116304, CVE-2026-116306, CVE-2026-116307, CVE-2026-116309, CVE-2026-116314, CVE-2026-116315, CVE-2026-116316, CVE-2026-116317, CVE-2026-116319, CVE-2026-116320, CVE-2026-116323, CVE-2026-116325, CVE-2026-116326, CVE-2026-116328, CVE-2026-116330, CVE-2026-116331, CVE-2026-116332, CVE-2026-116335, CVE-2026-116336 and 41 more.