CVE-2025-9803: lunary-ai/lunary version 1.9.34 is vulnerable to an account takeover due to improper authentication in the Goo

This month

HIGH 8.8DOWNGRADE

CVE-2025-9803 is a high-severity flaw (CVSS 8.8) affecting lunary. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.5% (top 60%)
CISA exploited list	No
Weakness	CWE-287, CWE-863
Published	2025-11-25
Last modified	2026-10-18

Publisher (CNA): huntr.dev · Vendor: lunary

Last updated 2026-10-18 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-11-25 01:15 UTCPublished CVE record published
2026-10-18 20:10 UTCUpdated Record last modified

lunary lunary DOWNGRADE

Affected: 1.9.34

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.9.34

1. Check installed version

apt-cache policy lunary || rpm -q lunary || lunary --version

2. No fixed release: DOWNGRADE to a release before 1.9.34 (Debian / Ubuntu)

apt-cache madison lunary sudo apt install lunary=<VERSION_BEFORE_1.9.34> sudo apt-mark hold lunary

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list lunary sudo dnf downgrade lunary-<VERSION_BEFORE_1.9.34> sudo dnf versionlock add lunary

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-9803?

lunary: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-9803 being exploited?

CVE-2025-9803 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-9803 affect?

CVE-2025-9803 affects lunary. Severity is high (CVSS 8.8). 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 c

How urgent is CVE-2025-9803?

Priority 46/100. High severity; Public exploit reference

Related CVEs

CVE-2025-5352 CRITICAL 9.6 UPGRADE A critical stored Cross-Site Scripting (XSS) vulnerability exists in the Analytics component of lunary-ai/luna
CVE-2025-4779 MEDIUM 6.1 UPGRADE lunary-ai/lunary versions prior to 1.9.24 are vulnerable to stored cross-site scripting (XSS)
CVE-2025-0281 MEDIUM 5.4 UPGRADE A stored cross-site scripting (XSS) vulnerability exists in lunary-ai/lunary versions 1.6.7 and earlier
CVE-2024-9099 HIGH 8.1 DOWNGRADE In lunary-ai/lunary version v1.4.29, the GET /projects API endpoint exposes both public and private API keys f
CVE-2024-9098 MEDIUM 6.1 UPGRADE In lunary-ai/lunary before version 1.4.30, a privilege escalation vulnerability exists where admins can invite

References

← Back to latest CVEs