Executive brief
A vulnerability in the stigmem-node library allows for the accidental disabling of security checks that verify the authenticity of plugins. If this setting is enabled in environments where file directories are shared or poorly protected, an attacker could replace legitimate plugins with malicious code. This could lead to a complete compromise of the application, including unauthorized data access or system control.
Technical details
The stigmem-node package (part of the Stigmem ecosystem) contains a vulnerability where plugin signature enforcement can be disabled via a single configuration flag without sufficient confirmation. This falls under CWE-494 (Download of Code Without Integrity Check). If an operator unintentionally enables this flag in an environment where plugin directories are writable by low-privileged users, an attacker can inject and execute unsigned, malicious plugin code. The vulnerability is exploited locally by placing a malicious plugin in the expected path after signature enforcement has been bypassed. A fix was introduced in version 0.9.0a2 which requires a second explicit acknowledgment value to disable signature checks.
Affected products
- Eidetic Labs stigmem-node < 0.9.0a2
Timeline
- 2026-05-18: patched: Version 0.9.0a2 released.
- 2026-05-29: advisory: GitHub Advisory GHSA-w7pm-9g55-mxfm published.
References
- https://github.com/eidetic-labs/stigmem/security/advisories/GHSA-w7pm-9g55-mxfm
- https://github.com/eidetic-labs/stigmem/blob/v0.9.0a2/CHANGELOG.md
- https://github.com/eidetic-labs/stigmem/blob/v0.9.0a2/SECURITY.md
- https://github.com/eidetic-labs/stigmem/releases/tag/v0.9.0a2
- https://api.github.com/repos/eidetic-labs/stigmem/security-advisories/GHSA-w7pm-9g55-mxfm