CVE-2026-105764

Immich through 3.3.1 contains a missing authorization vulnerability in the partner synchronization stream that allows authenticated partners to read Locked Folder asset metadata because sync queries do not exclude Locked visibility. Attackers with an active partner relationship can call POST /api/sync/stream with PartnerAssetsV2 and PartnerAssetExifsV1 types to obtain GPS coordinates, capture times, descriptions and camera details.

Immich, a photo and video management solution, has a reflected XSS vulnerability on the /auth/login page. An attacker can take over an authenticated user's account with a single link click.

A vulnerability has been found in immich-app Immich up to 2.7.5, affecting the checkSharedLinkAccess function in server/src/utils/access.ts within the Shared Link Preview Handler. Manipulation of the Password argument leads to improper authorization. The reported GitHub issue was closed as a duplicate.

Immich through 3.1.0 fails to properly enforce locked asset visibility when assets are locked through the single-asset endpoint, allowing them to remain accessible through shared albums and links. Attackers can read locked assets and their metadata by accessing existing shared albums or links, bypassing the locked visibility protection.

A broken access control vulnerability in Immich before version 3.0.3 in the PUT /albums/:id/user/:userId endpoint allows shared album editors to modify member roles without owner-only restrictions. Attackers with editor access can demote the album owner to editor and promote themselves to owner in sequential requests, gaining full control including deletion and eviction capabilities.

Immich before version 2.7.0 has a Stored XSS vulnerability in the 360° panorama viewer. An authenticated user can upload a malicious image whose OCR text is rendered unsanitized, allowing arbitrary JavaScript execution in other users' browsers.

Immich before version 2.6.0 has a credential disclosure vulnerability when authenticating to a shared album. The album password is transmitted in URL query parameters in a GET request to /api/shared-links/me, exposing it in browser history, proxy and server logs, and referrer headers.