# CVE-2026-82272: Immich Locked Assets Remain Readable Through Albums and Shared Links

> Attackers can read locked assets and metadata by accessing shared albums or links, bypassing visibility restrictions in Immich.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-7r4r-rw6m-57g4

## What is CVE-2026-82272?

CVE-2026-82272 is a high-severity missing authorization vulnerability in immich-app immich, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-82272 being exploited?

There is no known exploitation of CVE-2026-82272 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82272 is a high-severity missing authorization vulnerability in immich-app immich, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82272 in the wild and no public exploit code.

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-82272/ (Markdown: https://insights.sbomify.com/CVE-2026-82272/index.md)
```

## Sources

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

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