Account hijacking via unchecked OAuth state
Published Jul 11, 2025 · Updated Jul 11, 2025
Authentication failure in Immich before 1.132.0 allows attackers to hijack accounts through a forged OAuth authorization response. The OAuth callback accepts an unverified state value, and the /user-settings redirect automatically links the attacker's OAuth identity to the signed-in victim's account. Exploitation requires a public OAuth provider, an authenticated victim, and active interaction with a forged login URL or attacker-controlled page.
Summary
What happened
Authentication failure in Immich before 1.132.0 allows attackers to hijack accounts through a forged OAuth authorization response. The OAuth callback accepts an unverified state value, and the /user-settings redirect automatically links the attacker's OAuth identity to the signed-in victim's account. Exploitation requires a public OAuth provider, an authenticated victim, and active interaction with a forged login URL or attacker-controlled page.
The record
- CVE
- CVE-2025-43856
- Published
- Jul 11, 2025
- Updated
- Jul 11, 2025
- Vendor
- Immich
- Product
- Immich
- Classifications
- CWE-303, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 11, 2025CVE publishedPublication date reported by the CVE source.
- Jul 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.132.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo