Skip to main content
VulnerabilityPublished Updated

CVE-2026-76241: eidetic-labs stigmem · Download of Code Without Integrity Check

Affects eidetic-labs stigmemSource CVE Database V5

0
Compare

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

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.9.0a2
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/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
GitHubeidetic-labs/stigmempkg:github/eidetic-labs/stigmemOther 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, which requires a second explicit acknowledgment to disable plugin signature enforcement, preventing accidental or unauthorized disabling of this security feature. Until upgraded, ensure that plugin directories are not writable by less-trusted users to mitigate the risk of loading unsigned plugins.

Description

stigmem-node versions before 0.9.0a2 allow disabling plugin signature enforcement with a single configuration flag, which can lead to loading and executing unsigned plugin code if plugin directories are writable by less-trusted users. This vulnerability enables arbitrary code execution. The issue is fixed in version 0.9.0a2 by requiring a second explicit acknowledgment to disable signature enforcement.

References

Community reviews

Loading reviews…