CVE-2026-115332

waiting for further signalsZero needs more public information before it can validate it.

GHSA-fcf4-2wr8-2h4q ↗EUVD-2026-108134 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
uselotus lotus <= 0.10.2
ETK-2026-2459Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 04msince last run
1h 07mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+5h49m
0
+2h
+4h
+8h
+10h
+12h

description

Lotus through 0.10.2 does not safely handle certain subscription filter-key values in usage aggregation queries. An authenticated organization user able to create subscriptions may cause unintended SQL to run against the shared database.

mitigation

Restrict subscription creation to trusted organization users and review existing subscription filter keys for untrusted values. Upgrade from Lotus 0.10.2 or earlier after confirming that the selected newer release includes a fix.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 07m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 10:57Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-22 10:57Z
    ghsa: trigger signal, started the run
  2. 2026-10-22 10:57Z

this entry in the feed

GET /api/v1/feed/CVE-2026-115332

{
  "etk_id": "ETK-2026-2459",
  "cve_id": "CVE-2026-115332",
  "display_id": "CVE-2026-115332",
  "ghsa_id": "GHSA-fcf4-2wr8-2h4q",
  "euvd_id": "EUVD-2026-108134",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in Lotus subscription aggregation",
  "summary": "Lotus through 0.10.2 does not safely handle certain subscription filter-key values in usage aggregation queries. An authenticated organization user able to create subscriptions may cause unintended SQL to run against the shared database.",
  "mitigation": "Restrict subscription creation to trusted organization users and review existing subscription filter keys for untrusted values. Upgrade from Lotus 0.10.2 or earlier after confirming that the selected newer release includes a fix.",
  "vendor": "uselotus",
  "product": "lotus",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 0.10.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "lotus",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 66.74338241666666,
  "t0_at": "2026-10-22T10:57:48.791000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T10:57:48.791000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T10:57:48.791000+00:00",
      "url": "https://github.com/advisories/GHSA-fcf4-2wr8-2h4q"
    }
  }
}

published 2026-10-22 15:39Z
last change 2026-10-22 17:20Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.