CVE-2026-76242: eidetic-labs stigmem · Improper Certificate Validation
Affects eidetic-labs stigmemSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.9.0a2 as a priority.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% 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:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/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 introduces a pending approval flow requiring administrator fingerprint verification before accepting peer tokens. This official fix prevents unauthorized peer registration and mitigates the vulnerability.
Description
stigmem-node versions before 0.9.0a2 and version 0.9.0 have an improper certificate validation vulnerability. The software accepts federation peer key material during peer registration without requiring an out-of-band administrator fingerprint approval. This allows an attacker who can intercept or misdirect initial registration over the network to register a malicious peer and potentially access or tamper with federation traffic. The issue is fixed in version 0.9.0a2 by introducing a pending approval flow requiring administrator fingerprint verification.