Improper authorization in Immich lets users share other users' assets
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-285.
Summary
Immich versions before 3.2.0 are affected. The shared link creation API accepts an album and assets as independent fields but checks authorization only for the selected link type, which is improper authorization (CWE-285). An authenticated attacker who knows a victim's asset UUID can attach that asset to an anonymous shared link on the attacker's own album, exposing the victim's metadata, thumbnails and original file.
Written with Claude Haiku 5.5 from the sources below · 2026-11-05
Description from the CNA
Immich is a high-performance self-hosted photo and video management solution. Prior to 3.2.0, the shared-link creation API accepted albumId and assetIds as independent fields in server/src/services/shared-link.service.ts but authorized only the resource selected by the requested link type. An authenticated attacker who already knew a victim-owned asset UUID could select SharedLinkType.Album for an attacker-owned album while supplying that UUID in assetIds; SharedLinkService.create() persisted the unchecked association in shared_link_asset and made the victim asset available through the new anonymous shared-link credential. This exposed victim metadata, thumbnails, and the byte-identical original file and created a persistent sharing relationship that could be redistributed. This issue is fixed in version 3.2.0.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| immich-app | immich | before 3.2.0 | 3.2.0 | Patch available | CNA |
- immich Vendorimmich-app Affected before 3.2.0 Fixed in 3.2.0 Patch available CNA
CPE names Threatist (inferred) · 1
Inferred from how NVD named this product before; not given by a source.
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:futo:immich:*:*:*:*:*:*:*:* | — | — | immich-app |
- cpe:2.3:a:futo:immich:*:*:*:*:*:*:*:* Versions — — ·immich-app
Remediation
Upgrade Immich to version 3.2.0, which fixes this issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-05
- Fix · CNA immich (immich-app) Fixed in 3.2.0
Timeline
- 2026-10-30 Threatist record created from CVE-2026-119330
- 2026-11-05 CISA SSVC decision points changed
- 2026-11-05 Priority changed: LOW → MEDIUM
References
More immich-app vulnerabilities
- TI-2026-38703 immich: One-click account takeover via XSS in login page continue redirect CVSS 3.1CRITICAL 9.6
- TI-2026-19252 immich API Key Privilege Escalation vulnerability CVSS 3.1HIGH 8.8
- TI-2026-65721 immich-app Immich Shared Link Preview access.ts checkSharedLinkAccess improper authorization CVSS 4.0MEDIUM 6.9
- TI-2026-68375 Code injection in Immich lets authenticated users run code via SVG CVSS 4.0HIGH 7.7
- TI-2026-83367 Unauthenticated path injection in Immich machine-learning service CVSS 3.1MEDIUM 6.5
- TI-2025-28440 immich allows account hijacking through oauth2 CVSS 4.0HIGH 7.3
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences