CVE Intelligence
High Injection

CVE-2026-115332 — Lotus through 0.10.2 SQL Injection via Subscription Filter Keys

Lotus through 0.10.2 contains an sql injection vulnerability that allows authenticated organization users to inject SQL by registering crafted subscription_filter_keys that bypass keyword-only validation. Attackers can create subscriptions using the malicious key, which is rendered as an unquoted group-by identifier, to inject SQL into usage aggregation queries against the shared multi-tenant database.

Published Oct 22, 2026 · Updated Oct 22, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.3%
ahead of 23% of scored CVEs · Oct 27, 2026
Affects
Uselotus
Lotus
CVSS base
8.8
High · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Uselotus Lotus).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Uselotus Lotus ≤ 0.10.2 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.7 CVSS 4.0 High — — disclosure@vulncheck.com via NIST National Vulnerability Database
8.7 CVSS 4.0 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
8.8 CVSS 3.1 High 2.8 5.9 disclosure@vulncheck.com via NIST National Vulnerability Database
8.8 CVSS 3.1 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-89 · SQL Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 23, 2026 → Oct 27, 2026 · 5 reading(s) · max 0.30%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Deferred
    Oct 22, 2026 · NIST National Vulnerability Database
  • Affected products added · uselotus/lotus
    Oct 22, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 22, 2026
  • CVSS changed · 8.8
    Oct 22, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 22, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 22, 2026 · Alertas do Telegram
  • CVE published
    Oct 22, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 22, 2026 – Oct 22, 2026
  • 1× Official description updated · Oct 22, 2026 – Oct 22, 2026

References

4 on the record

Elsewhere on this site

Uselotus
every CVE for this vendor
Injection
same class
CWE-89
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-115329 Lotus through 0.10.2 Cross-Organization IDOR via SubscriptionViewSet 6d
  • CVE-2026-115330 Lotus through 0.10.2 SQL Injection via Custom SQL Billable Metrics 6d
  • CVE-2026-115331 Lotus through 0.10.2 SQL Injection via Metric Property Names and Filters 6d
  • CVE-2026-115333 Lotus through 0.10.2 Improper Authentication via Event Ingestion API Key Prefix 6d
  • CVE-2026-115334 Lotus through 0.10.2 Authorization Bypass via switch_organization Endpoint 6d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-115332 is "Lotus through 0.10.2 SQL Injection via Subscription Filter Keys", rated High. It affects Lotus (Uselotus); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 0.30% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.