CVE-2025-9803: lunary-ai/lunary · Improper Authentication
Affects lunary-ai lunary-ai/lunarySource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical · fixed in 1.9.35 : patch lunary-ai/lunary as a priority.
Data as of 10/25/2026, 09:03:59 UTC
- Exploitation
Not in CISA KEV, no exploitation reported
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- 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:NWhat to do
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
The primary mitigation is to upgrade lunary-ai/lunary to version 1.9.35 or later, where the 'aud' claim verification is correctly implemented. Organizations should audit their OAuth token validation processes to ensure all tokens are verified against the expected audience and issuer fields. Implement additional monitoring for anomalous login patterns and token usage to detect potential misuse. Employ multi-factor authentication (MFA) to reduce the risk of account takeover even if token validation is bypassed. Educate users about phishing risks associated with OAuth login flows. For environments where immediate upgrade is not possible, consider disabling Google OAuth login temporarily or restricting access to trusted IP ranges. Regularly review OAuth client configurations and permissions to minimize attack surface.
Description
lunary-ai/lunary version 1.9.34 is vulnerable to an account takeover due to improper authentication in the Google OAuth integration. The application fails to verify the 'aud' (audience) field in the access token issued by Google, which is crucial for ensuring the token is intended for the application. This oversight allows attackers to use tokens issued to malicious applications to gain unauthorized access to user accounts. The issue is resolved in version 1.9.35.
Impact
For European organizations, this vulnerability poses a significant risk to user account security and data confidentiality. Organizations relying on lunary-ai/lunary for critical business functions or sensitive data management could face unauthorized data access, leading to data breaches, loss of intellectual property, and reputational damage. The improper authentication flaw undermines trust in OAuth-based single sign-on, potentially exposing users to account takeover through token misuse. Attackers could impersonate legitimate users, access confidential communications, or manipulate data, impacting business operations and compliance with GDPR and other data protection regulations. The lack of availability impact means service disruption is unlikely, but the confidentiality and integrity risks are severe. Organizations with extensive cloud integration and Google OAuth usage are particularly vulnerable.
Weaknesses
- CWE-287Improper Authentication (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.