GitHub Advisoryadvisory · PyPI

GHSA-w7pm-9g55-mxfm stigmem-node's unsigned plugin override could be enabled without a second explicit acknowledgment

HIGH Published 2026-05-29 Modified 2026-05-29 Official page ↗
Ecosystem
PyPI
Packages
stigmem-node
Severity
High
CVSS vector
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
Weaknesses
CWE-494
Reviewed
2026-05-29

Affected packages

• PyPI stigmem-node: < 0.9.0a2 → fixed in 0.9.0a2

Description

Impact A single configuration flag could disable plugin signature enforcement. If an operator unintentionally carried that setting into an environment where plugin paths are writable by less-trusted users, unsigned plugin code could be loaded. Patches Patched in 0.9.0a2. Disabling plugin signature enforcement now requires a second explicit acknowledgment value. Workarounds Before upgrading, keep plugin signing required in all shared or production environments and ensure plugin directories are not writable by untrusted users. Upgrade Upgrade to the patched release: ```bash pip install --upgrade --pre stigmem-node ``` If developers install through the Stigmem meta-package instead, they should use the matching extra for deployments, for example: ```bash pip install --upgrade --pre 'stigmem[node]' ``` Resources • Release: https://github.com/eidetic-labs/stigmem/releases/tag/v0.9.0a2 • Changelog: https://github.com/eidetic-labs/stigmem/blob/v0.9.0a2/CHANGELOG.md#L14-L35 • Security policy and posture: https://github.com/eidetic-labs/stigmem/blob/v0.9.0a2/SECURITY.md

Related

Weakness · CWE (1)

  • CWE-494 Download of Code Without Integrity Check weakness

References