Advisory record · GHSA-w7pm-9g55-mxfm

stigmem-node's unsigned plugin override could be enabled without a second explicit acknowledgment

CVSS 7.3 HighEPSS 0.0011 · 1st percentile

Published by the GitHub Advisory Database at 29 May 2026, 22:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
stigmem-nodePyPI<0.9.0a20.9.0a2
Identifiers
GHSA-w7pm-9g55-mxfm · CVE-2026-76241
Weakness (CWE)
CWE-494
Published
29 May 2026
Updated
20 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The stigmem-node package is affected in versions before 0.9.0a2. A single configuration flag could turn off plugin signature enforcement, so if that setting carried into an environment where less-trusted users can write plugin paths, unsigned plugin code could be loaded. Upgrade to 0.9.0a2, which now requires a second explicit acknowledgment value before signature enforcement can be disabled.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.3 High 4.0 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 CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0011, the 1st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:39 UTC First seen by agentprime
  2. 31 Oct 2026, 14:39 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.