CVE-2026-76241stigmem Plugin Signature Enforcement Bypass via Configuration
Updated under an hour ago ()
Does this affect you?
It affects eidetic-labs stigmem. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
stigmem-node 0.9.0a1 allows plugin signature enforcement to be disabled via a single configuration flag without a second explicit acknowledgment. If that setting is carried into an environment where plugin directories are writable by less-trusted users, unsigned (potentially malicious) plugin code could be loaded and executed, resulting in arbitrary code execution. Fixed in 0.9.0a2, which requires a second explicit acknowledgment to disable signature enforcement.
- CVSS
- 7.3 HIGH (v4.0, CNA)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
- Weakness (CWE)
- CWE-494
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- VulnCheck
- NVD analysis
- Deferred
- Record last updated
- Aug 21, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
eidetic-labs stigmem eidetic_labs:stigmem (from the name) | before 0.9.0a2; 0.9.0a2 not affected | CNA record |
References
- https://github.com/eidetic-labs/stigmem/security/advisories/GHSA-w7pm-9g55-mxfmvendor-advisory
- https://www.vulncheck.com/advisories/stigmem-plugin-signature-enforcement-bypass-via-configurationthird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.