# CVE-2025-43856: immich allows account hijacking through oauth2

> Attackers can hijack user accounts by exploiting missing OAuth2 state validation, allowing unauthorized account linking and subsequent access.

- **Severity:** High 7.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Jul 2025
- **Updated:** 11 Jul 2025
- **Also known as:** GHSA-3832-6r8h-9cfm

## What is CVE-2025-43856?

CVE-2025-43856 is a high-severity vulnerability in immich-app immich, published on 11 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

immich is a high performance self-hosted photo and video management solution. Prior to 1.132.0, immich is vulnerable to account hijacking through oauth2, because the state parameter is not being checked. The oauth2 state parameter is similar to a csrf token, so when the user starts the login flow this unpredictable token is generated and somehow saved in the browser session and passed to the identity provider, which will return the state parameter when redirecting the user back to immich. Before the user is logged in that parameter needs to be verified to make sure the login was actively initiated by the user in this browser session. On it's own, this wouldn't be too bad, but when immich uses the /user-settings page as a redirect_uri, it will automatically link the accounts if the user was already logged in. This means that if someone has an immich instance with a public oauth provider (like google), an attacker can - for example - embed a hidden iframe in a webpage or even just send the victim a forged oauth login url with a code that logs the victim into the attackers oauth account and redirects back to immich and links the accounts. After this, the attacker can log into the victims account using their own oauth credentials. This vulnerability is fixed in 1.132.0.

Weakness: CWE-303 (Incorrect Implementation of Authentication Algorithm)

## Which versions are affected by CVE-2025-43856?


## How do I fix CVE-2025-43856?

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

## Is CVE-2025-43856 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-43856 and fix it if it is affected.

What it is: CVE-2025-43856 is a high-severity vulnerability in immich-app immich, published on 11 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-43856 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-2025-43856/ (Markdown: https://insights.sbomify.com/CVE-2025-43856/index.md)
```

## Sources

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

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