CVE-2024-5386: lunary-ai/lunary · Excessive Attack Surface
Affects lunary-ai/lunarySource CVE Database V5
Not known to be exploited · CVSS 9.6 Critical.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| lunary-ailunary-ai/lunary | 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
- Immediately restrict access to password reset functionality to trusted roles only, ensuring that low-privilege users like 'viewer' cannot trigger password reset token generation for other accounts.
- Implement strict server-side validation and authorization checks to confirm that password reset tokens are only issued to legitimate requesters for their own accounts.
- Monitor logs for unusual password reset requests originating from viewer role users or other low-privilege accounts.
- Employ multi-factor authentication (MFA) on all user accounts to reduce the impact of compromised credentials.
- Isolate and segment systems running lunary-ai/lunary to limit lateral movement in case of compromise.
- Engage with the vendor for timely patches or updates addressing this vulnerability and apply them as soon as available.
- Conduct internal security audits and penetration testing focusing on access control and token management mechanisms.
- Educate users about phishing and social engineering risks that could compound the vulnerability exploitation.
- Consider implementing rate limiting and anomaly detection on password reset endpoints to detect and block abuse attempts.
Description
In lunary-ai/lunary version 1.2.2, an account hijacking vulnerability exists due to a password reset token leak. A user with a 'viewer' role can exploit this vulnerability to hijack another user's account by obtaining the password reset token. The vulnerability is triggered when the 'viewer' role user sends a specific request to the server, which responds with a password reset token in the 'recoveryToken' parameter. This token can then be used to reset the password of another user's account without authorization. The issue results from an excessive attack surface, allowing lower-privileged users to escalate their privileges and take over accounts.