CVE-2026-76240: eidetic-labs stigmem · SQL Injection
Affects eidetic-labs stigmemSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 0.9.0a2 soon.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.9.0a2
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade eidetic-labs stigmem to 0.9.0a2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| eidetic-labsstigmem | Affected
| Fixed in
|
GitHubeidetic-labs/stigmempkg:github/eidetic-labs/stigmemOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to stigmem-node version 0.9.0a2 or later, which includes proper identifier quoting and validation to prevent SQL injection. As a temporary workaround, ensure that schema names are only configured from trusted deployment configurations and not derived from user or tenant input.
Description
stigmem-node versions before 0.9.0a2 and version 0.9.0 contain an SQL injection vulnerability due to improper neutralization of special elements in SQL commands. The vulnerability arises because schema identifiers are interpolated into SQL strings without proper quoting, and these schema names can be influenced by operator-controlled input. The issue is fixed in version 0.9.0a2 by adding identifier quoting and validation. As a workaround, schema names should only be configured from trusted deployment configurations.