Skip to main content
VulnerabilityPublished Updated

CVE-2024-9095: lunary-ai/lunary · Missing Authorization

Affects lunary-ai/lunarySource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.0 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GitHublunary-ai/lunarypkg:github/lunary-ai/lunaryOther threatsAffected
  • =1.4.28
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately restrict access to the /bigquery API endpoint by implementing strict role-based access control (RBAC) or attribute-based access control (ABAC) to ensure only authorized administrators can initiate data exports.
  2. Introduce access control middleware that verifies user permissions before processing export requests.
  3. Disable the `config.DATA_WAREHOUSE_EXPORTS_ALLOWED` flag if data exports are not essential or restrict it to trusted environments only.
  4. Monitor and audit all data export activities, especially those involving BigQuery, to detect anomalous or unauthorized usage.
  5. Rotate all potentially exposed credentials, including API keys and passwords, following any suspected exploitation.
  6. Apply network segmentation to limit the exposure of the lunary-ai/lunary service to trusted internal users only.
  7. Engage with the vendor or community to obtain patches or updates addressing this vulnerability as soon as they become available.
  8. Conduct regular security assessments and penetration testing focusing on authorization controls within the application.

Description

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 keys. The route is protected by a config check (`config.DATA_WAREHOUSE_EXPORTS_ALLOWED`), but it does not verify the user's access level or implement any access control middleware. This vulnerability can lead to the extraction of sensitive data, disruption of services, credential compromise, and service integrity breaches.

References

Community reviews

Loading reviews…