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.
CVE-2026-76241
HIGHPre-NVD 7.37.3—Trending — 4 sources updated this week
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(medium)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity73% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 0%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 19, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026Patch available. Sources: github.
generic
stigmem Plugin Signature Enforcement Bypass via Configuration | Advisories | VulnCheck
https://www.vulncheck.com/advisories/stigmem-plugin-signature-enforcement-bypass-via-configurationgithub Patch Available
Unsigned plugin override could be enabled without a second explicit acknowledgment · Advisory · eidetic-labs/stigmem · GitHub
Affected: 0.9.0a2. Disabling plugin signature enforcement now requires a second explicit ac
https://github.com/eidetic-labs/stigmem/security/advisories/GHSA-w7pm-9g55-mxfmVendor Advisories for CVE-2026-76241(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 01:41 UTCEG score recompute
- 2026-08-21 01:41 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 14:00 UTCGHSA enrichment
- 2026-08-20 02:08 UTCGHSA enrichment
- 2026-08-19 14:26 UTCEG score recompute
- 2026-08-19 14:12 UTCEG score recompute
- 2026-08-19 14:12 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-76241?
CVE-2026-76241 is a high vulnerability published on August 19, 2026. 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…
When was CVE-2026-76241 disclosed?
CVE-2026-76241 was first published in the National Vulnerability Database on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76241 actively exploited?
CVE-2026-76241 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.5% of all scored CVEs.
What is the CVSS score of CVE-2026-76241?
CVE-2026-76241 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-76241?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76241, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76241
Is Your Infrastructure Affected by CVE-2026-76241?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.