Skip to main content
VulnerabilityPublished Updated

CVE-2026-76245: eidetic-labs stigmem · Insufficient Verification of Data Authenticity

Affects eidetic-labs stigmemSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 0.9.0a2 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% 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:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
eidetic-labsstigmemAffected
  • <0.9.0a2
Fixed in
  • 0.9.0a2
PyPIstigmem-nodepkg:pypi/stigmem-nodeOther threatsAffected
  • =0.9.0
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 stigmem-node to version 0.9.0a2 or later, where the issue is fixed by using a canonical millisecond-based validation path. No other mitigations are indicated.

Description

stigmem (pip package stigmem-node) version 0.9.0a1 has a vulnerability in its federation peer-token validation due to a timestamp-handling mismatch. This causes valid peer tokens to be incorrectly treated as expired, impacting the availability and reliability of authenticated federation flows. The issue is resolved in version 0.9.0a2 by adopting a canonical millisecond-based validation method.

References

Community reviews

Loading reviews…