# CVE-2026-115331: Lotus through 0.10.2 SQL Injection via Metric Property Names and Filters


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-v5rh-mv3x-53gj

## What is CVE-2026-115331?

CVE-2026-115331 is a high-severity vulnerability in uselotus lotus, published on 22 Oct 2026. 

### Official description

Lotus through 0.10.2 contains an sql injection vulnerability that allows authenticated organization users to inject SQL by supplying crafted billable metric property_name or categorical filter values. Attackers can embed SQL in values rendered unescaped into Jinja-generated counter, gauge and rate metric queries to access the database shared by all tenants.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-115331?


## How do I fix CVE-2026-115331?

No fix has been published for CVE-2026-115331 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115331 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115331 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115331 and fix it if it is affected.

What it is: CVE-2026-115331 is a high-severity vulnerability in uselotus lotus, published on 22 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115331 exists.

Affected product: uselotus lotus. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115331/ (Markdown: https://insights.sbomify.com/CVE-2026-115331/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115331
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115331
- OSV: https://osv.dev/vulnerability/CVE-2026-115331

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115331/
Summaries are generated and may contain mistakes; the official description above is the record.