Live › vulnerability › CVE-2026-115330
Go to dashboardLotus (uselotus, open-source usage billing) through 0.10.2 lets any logged-in user, including self-registered ones, create a 'custom' metric whose custom_sql runs on the shared Postgres database. validate_custom_sql checks only the first statement (sqlparse parsed_sql[0]), so after a ';' the attacker can run any SQL. That reads or changes every tenant's data, and DB errors are echoed back, which enables extraction. The same researcher reports related injection through property_name and subscription filters, plus an org-switch authorization flaw. No fixed version has been published.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| lotus | github | <= 0.10.2 | – |
0.10.2 (check the image tag or the git tag you deployed) is affectedcustom and look for ';' in custom_sql0.10.2 is the latest)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Lotus through 0.10.2 contains an sql injection vulnerability that allows authenticated organization users to execute arbitrary SQL by appending stacked statements to custom metric queries. Attackers can submit semicolon-separated SQL through POST /app/metrics/, bypassing first-statement-only validation, to read or modify data across all tenants.
This page as .md · .json · in your agent: get_signal("CVE-2026-115330")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.