CVE-2025-9803: lunary-ai/lunary version 1.9.34 is vulnerable to an account takeover due to improper authentication in
Source GCVE Database
Not known to be exploited · CVSS 9.3 Critical : upgrade to 1.9.35 as a priority.
Data as of 18 Nov 2026, 02:27 UTC
- Patch
- Available – fixed in 1.9.35
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade lunary-ai/lunary to 1.9.35.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHublunary-ai/lunarypkg:github/lunary-ai/lunaryOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade lunary-ai/lunary to version 1.9.35 or later, where the issue with improper verification of the 'aud' field in Google OAuth tokens is fixed. No other mitigations are indicated.
Description
lunary-ai/lunary version 1.9.34 contains a critical vulnerability in its Google OAuth integration that allows account takeover. The application does not verify the 'aud' (audience) field in Google-issued access tokens, enabling attackers to use tokens meant for other applications to access user accounts. This flaw is fixed in version 1.9.35.