Account takeover via unchecked OAuth token audience
Published Nov 25, 2025 · Updated Nov 25, 2025
Improper authentication in Lunary before 1.9.35 allows remote attackers to take over accounts through a Google OAuth access token. The Google OAuth callback accepts an access token without confirming that its aud claim names the Lunary client, so a token issued to an attacker-controlled application is treated as valid. A victim must authorize the malicious Google application; the resulting token lets the attacker sign in as that victim and access or alter the victim's Lunary data.
Summary
What happened
Improper authentication in Lunary before 1.9.35 allows remote attackers to take over accounts through a Google OAuth access token. The Google OAuth callback accepts an access token without confirming that its aud claim names the Lunary client, so a token issued to an attacker-controlled application is treated as valid. A victim must authorize the malicious Google application; the resulting token lets the attacker sign in as that victim and access or alter the victim's Lunary data.
The record
- CVE
- CVE-2025-9803
- Published
- Nov 25, 2025
- Updated
- Nov 25, 2025
- Vendor
- Lunary
- Product
- Lunary
- Classifications
- CWE-287, CWE-863, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 25, 2025CVE publishedPublication date reported by the CVE source.
- Nov 25, 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=unspecified <1.9.35
What conditions does exploitation require?
What is affected?
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