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.
- 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
- None listed
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
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.
Sources
Also known as GHSA-3832-6r8h-9cfm.