CVE-2026-76244: eidetic-labs stigmem · Cleartext Transmission
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 17 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% 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: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 17 Nov 2026.
What to do
Upgrade eidetic-labs stigmem to 0.9.0a2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| eidetic-labsstigmem | Affected
| Fixed in
|
AI-suggested
Operators should ensure mTLS is enabled when binding federation to non-loopback addresses to protect federation traffic. Upgrading to version 0.9.0a2 or later, where this issue is presumably fixed, is recommended.
Description
stigmem-node in eidetic-labs stigmem has a vulnerability where federation traffic can be transmitted without mTLS protection if non-loopback endpoints are enabled and mTLS is explicitly disabled. This insecure default configuration allows sensitive federation traffic to be exposed in cleartext, risking interception and man-in-the-middle attacks.