Advisory

GHSA-w7pm-9g55-mxfm

Also known as: CVE-2026-76241

Summary

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

Details

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:

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:

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

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-05-29 22:17 UTC
Modified
2026-08-20 04:04 UTC

Affected packages and fixes

stigmem-node

PyPI · All systems

Affected

  • introduced 0, fixed 0.9.0a2 (ecosystem)

Fixed versions

0.9.0a2

Fix

  • Fixed version 0.9.0a2
    pip install --upgrade stigmem-node==0.9.0a2

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences