Cross-Site Request Forgery (CSRF) in lunary-ai/lunary
Description
A Cross-Site Request Forgery (CSRF) vulnerability exists in lunary-ai/lunary version 1.2.34 due to overly permissive CORS settings. This vulnerability allows an attacker to sign up for and create projects or use the instance as if they were a user with local access. The main attack vector is for instances hosted locally on personal machines, which are not publicly accessible. The CORS settings in the backend permit all origins, exposing unauthenticated endpoints to CSRF attacks.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Lunary 1.2.34 has a CSRF vulnerability due to overly permissive CORS, allowing attackers to sign up or create projects on local instances.
Vulnerability
The vulnerability is a Cross-Site Request Forgery (CSRF) in lunary-ai/lunary version 1.2.34. The root cause is overly permissive CORS (Cross-Origin Resource Sharing) settings in the backend, which allow all origins. This misconfiguration makes unauthenticated endpoints susceptible to CSRF attacks [1][2].
Exploitation
To exploit this, an attacker would craft a malicious web page or link that, when visited by a victim who has a local lunary instance running, triggers a forged request. The attack vector is primarily for instances hosted locally on personal machines that are not publicly accessible. No prior authentication is needed because the vulnerable endpoints are unauthenticated [1][2].
Impact
Successful exploitation enables an attacker to sign up for new accounts and create projects on the victim's local instance, impersonating a legitimate user with local access. This can lead to unauthorized use of the instance's resources and potential data exposure within the created projects [1].
Mitigation
The issue exists in version 1.2.34. As of the publication date, a fix has not been detailed, but the recommended mitigation is to restrict CORS policies to trusted origins only, especially for unauthenticated endpoints, and to ensure instances are not exposed to untrusted networks [1][2].
AI Insight generated on May 20, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
lunarynpm | < 1.4.10 | 1.4.10 |
@lunary/backendnpm | < 1.4.10 | 1.4.10 |
Affected products
3- ghsa-coords2 versions
< 1.4.10+ 1 more
- (no CPE)range: < 1.4.10
- (no CPE)range: < 1.4.10
- lunary-ai/lunary-ai/lunaryv5Range: unspecified
Patches
13451fcd7b9d9Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
4News mentions
0No linked articles in our index yet.