# CVE-2026-119330: Immich: A regular user can create SharedLink for album/asset belonging to another user through CreateSharedLink API


- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-g4w3-c888-cr93

## What is CVE-2026-119330?

CVE-2026-119330 is a low-severity vulnerability in immich-app immich, published on 30 Oct 2026. 

### Official description

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.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-119330?


## How do I fix CVE-2026-119330?

No fix has been published for CVE-2026-119330 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119330 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119330 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119330 and fix it if it is affected.

What it is: CVE-2026-119330 is a low-severity vulnerability in immich-app immich, published on 30 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119330 exists.

Affected product: immich-app immich. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119330/ (Markdown: https://insights.sbomify.com/CVE-2026-119330/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119330
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119330
- OSV: https://osv.dev/vulnerability/CVE-2026-119330

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119330/
Summaries are generated and may contain mistakes; the official description above is the record.
