CVE-2026-115331: high-severity vulnerability in uselotus lotus
Lotus through 0.10.2 SQL Injection via Metric Property Names and Filters
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.7epss 0.4%
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.
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
Affected products
uselotus · lotusRelated CVEs — uselotus lotus
In the same product, most dangerous first.
CVE-2026-115332HIGHLotus through 0.10.2 SQL Injection via Subscription Filter KeysEPSS 0.4%CVE-2026-115330HIGHLotus through 0.10.2 SQL Injection via Custom SQL Billable MetricsEPSS 0.4%CVE-2026-115333HIGHLotus through 0.10.2 Improper Authentication via Event Ingestion API Key PrefixEPSS 0.4%CVE-2026-115334HIGHLotus through 0.10.2 Authorization Bypass via switch_organization EndpointEPSS 0.4%CVE-2026-115329MEDIUMLotus through 0.10.2 Cross-Organization IDOR via SubscriptionViewSetEPSS 0.3%
References
https://github.com/uselotus/lotushttps://github.com/uselotus/lotus/blob/0.10.2/backend/metering_billing/aggregation/counter_query_templates.py#L14https://hackmd.io/@leediay/BkUc3WL2Mxhttps://www.vulncheck.com/advisories/lotus-through-0.10.2-sql-injection-via-metric-property-names-and-filters