CyberSecBulletin

Lunary vulnerabilities

We track 26 vulnerabilities in Lunary products. 26 are rated high or critical, and none are known to be exploited. The most recent was published on February 2, 2026.

26vulnerabilities
6critical
20high
0exploited
8.2average CVSS score

Latest Lunary vulnerabilities

  • 8.8 High severity

    lunary-ai/lunary: Excessive Attack Surface

    CVE-2024-5386Lunary-ai

    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 vulnerabilit

  • 8.8 High severity

    lunary-ai/lunary: Incorrect Authorization

    CVE-2025-9803Lunary-ai

    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

  • 9.6 Critical severity

    lunary-ai/lunary: Improper Neutralization of Input During Web Page Generation

    CVE-2025-5352Lunary-ai

    A critical stored Cross-Site Scripting (XSS) vulnerability exists in the Analytics component of lunary-ai/lunary versions up to 1.9.23, where the NEXT_PUBLIC_CUSTOM_SCRIPT environment variable is directly injected into the DOM using dangerouslySetInnerHTML wit

  • 8.1 High severity

    lunary-ai/lunary: Exposure of Sensitive Information Through Metadata

    CVE-2024-9099Lunary-ai

    In lunary-ai/lunary version v1.4.29, the GET /projects API endpoint exposes both public and private API keys for all projects to users with minimal permissions, such as Viewers or Prompt Editors. This vulnerability allows unauthorized users to retrieve sensiti

  • 7.1 High severity

    lunary-ai/lunary: Missing Authorization

    CVE-2024-9096Lunary-ai

    In lunary-ai/lunary version 1.4.28, the /checklists/:id route allows low-privilege users to modify checklists by sending a PATCH request. The route lacks proper access control, such as middleware to ensure that only authorized users (e.g., project owners or ad

  • 9.8 Critical severity

    lunary-ai/lunary: Missing Authorization

    CVE-2024-9095Lunary-ai

    In lunary-ai/lunary version v1.4.28, the /bigquery API route lacks proper access control, allowing any logged-in user to create a Datastream to Google BigQuery and export the entire database. This includes sensitive data such as password hashes and secret API

  • 7.5 High severity

    lunary-ai/lunary: Missing Authorization

    CVE-2024-8999Lunary-ai

    lunary-ai/lunary version v1.4.25 contains an improper access control vulnerability in the POST /api/v1/data-warehouse/bigquery endpoint. This vulnerability allows any user to export the entire database data by creating a stream to Google BigQuery without prope

  • 7.5 High severity

    lunary-ai/lunary: Inefficient Regular Expression Complexity

    CVE-2024-8998Lunary-ai

    A Regular Expression Denial of Service (ReDoS) vulnerability exists in lunary-ai/lunary version git f07a845. The server uses the regex /{.*?}/ to match user-controlled strings. In the default JavaScript regex engine, this regex can take polynomial time to matc

  • 7.5 High severity

    lunary-ai/lunary: Inefficient Regular Expression Complexity

    CVE-2024-8789Lunary-ai

    Lunary-ai/lunary version git 105a3f6 is vulnerable to a Regular Expression Denial of Service (ReDoS) attack. The application allows users to upload their own regular expressions, which are then executed on the server side. Certain regular expressions can have

  • 7.3 High severity

    lunary-ai/lunary: Improper Resolution of Path Equivalence

    CVE-2024-8765Lunary-ai

    In lunary-ai/lunary, the privilege check mechanism is flawed in version git afc5df4. The system incorrectly identifies certain endpoints as public if the path contains '/auth/' anywhere within it. This allows unauthenticated attackers to access sensitive endpo

  • 7.5 High severity

    lunary-ai/lunary: Inefficient Regular Expression Complexity

    CVE-2024-8764Lunary-ai

    A vulnerability in lunary-ai/lunary, as of commit be54057, allows users to upload and execute arbitrary regular expressions on the server side. This can lead to a Denial of Service (DoS) condition, as certain regular expressions can cause excessive resource co

  • 7.5 High severity

    lunary-ai/lunary: Inefficient Regular Expression Complexity

    CVE-2024-8763Lunary-ai

    A Regular Expression Denial of Service (ReDoS) vulnerability exists in the lunary-ai/lunary repository, specifically in the compileTextTemplate function. The affected version is git be54057. An attacker can exploit this vulnerability by manipulating the regula

  • 7.5 High severity

    lunary-ai/lunary: Authorization Bypass Through User-Controlled Key

    CVE-2024-11137Lunary-ai

    An Insecure Direct Object Reference (IDOR) vulnerability exists in the `PATCH /v1/runs/:id/score` endpoint of lunary-ai/lunary version 1.6.0. This vulnerability allows an attacker to update the score data of any run by manipulating the id parameter in the requ

  • 8.1 High severity

    lunary-ai/lunary: Missing Authorization

    CVE-2024-10762Lunary-ai

    In lunary-ai/lunary before version 1.5.9, the /v1/evaluators/ endpoint allows users to delete evaluators of a project by sending a DELETE request. However, the route lacks proper access control, such as middleware to ensure that only users with appropriate rol

  • 7.3 High severity

    lunary-ai/lunary: Incorrect Authorization

    CVE-2024-10275Lunary-ai

    In version 1.5.5 of lunary-ai/lunary, a vulnerability exists where admins, who do not have direct permissions to access billing resources, can change the permissions of existing users to include billing permissions. This can lead to a privilege escalation scen

  • 7.5 High severity

    lunary-ai/lunary: Missing Authorization

    CVE-2024-10272Lunary-ai

    lunary-ai/lunary is vulnerable to broken access control in the latest version. An attacker can view the content of any dataset without any kind of authorization by sending a GET request to the /v1/datasets endpoint without a valid authorization token.

  • 7.5 High severity

    lunary-ai/lunary: Allocation of Resources Without Limits or Throttling

    CVE-2024-3760Lunary-ai

    In lunary-ai/lunary version 1.2.7, there is a lack of rate limiting on the forgot password page, leading to an email bombing vulnerability. Attackers can exploit this by automating forgot password requests to flood targeted user accounts with a high volume of

  • 8.1 High severity

    lunary-ai/lunary: Insecure Storage of Sensitive Information

    CVE-2024-3502Lunary-ai

    In lunary-ai/lunary versions up to and including 1.2.5, an information disclosure vulnerability exists where account recovery hashes of users are inadvertently exposed to unauthorized actors. This issue occurs when authenticated users inspect responses from `G

  • 8.1 High severity

    lunary-ai/lunary: Insecure Storage of Sensitive Information

    CVE-2024-3501Lunary-ai

    In lunary-ai/lunary versions up to and including 1.2.5, an information disclosure vulnerability exists due to the inclusion of single-use tokens in the responses of `GET /v1/users/me` and `GET /v1/users/me/org` API endpoints. These tokens, intended for sensiti

  • 8.1 High severity

    lunary-ai/lunary: Incorrect Authorization

    CVE-2024-3379Lunary-ai

    In lunary-ai/lunary versions 1.2.2 through 1.2.6, an incorrect authorization vulnerability allows unprivileged users to re-generate the private key for projects they do not have access to. Specifically, a user with a 'Member' role can issue a request to regene

  • 9.8 Critical severity

    lunary-ai/lunary: Improper Neutralization of Special Elements used in an SQL Command

    CVE-2024-7456Lunary-aiEPSS 1.41%

    A SQL injection vulnerability exists in the `/api/v1/external-users` route of lunary-ai/lunary version v1.4.2. The `order by` clause of the SQL query uses `sql.unsafe` without prior sanitization, allowing for SQL injection. The `orderByClause` variable is cons

  • 9.1 Critical severity

    lunary-ai/lunary: Missing Authorization

    CVE-2024-7475Lunary-ai

    An improper access control vulnerability in lunary-ai/lunary version 1.3.2 allows an attacker to update the SAML configuration without authorization. This vulnerability can lead to manipulation of authentication processes, fraudulent login requests, and theft

  • 8.1 High severity

    lunary-ai/lunary: Cross-Site Request Forgery

    CVE-2024-6862Lunary-ai

    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 a

  • 9.8 Critical severity

    lunary-ai/lunary: Incorrect Authorization

    CVE-2024-4146Lunary-ai

    In lunary-ai/lunary version v1.2.13, an incorrect authorization vulnerability exists that allows unauthorized users to access and manipulate projects within an organization they should not have access to. Specifically, the vulnerability is located in the `chec

  • 8.1 High severity

    lunary-ai/lunary: Authorization Bypass Through User-Controlled Key

    CVE-2024-4151Lunary-ai

    An Improper Access Control vulnerability exists in lunary-ai/lunary version 1.2.2, where users can view and update any prompts in any projects due to insufficient access control checks in the handling of PATCH and GET requests for template versions. This vulne

  • 9.1 Critical severity

    lunary-ai/lunary: Incorrect Authorization

    CVE-2024-1740Lunary-ai

    In lunary-ai/lunary version 1.0.1, a vulnerability exists where a user removed from an organization can still read, create, modify, and delete logs by re-using an old authorization token. The lunary web application communicates with the server using an 'Author