stigmem-node
Affected
- introduced
0, fixed0.9.0a2(ecosystem)
Fixed versions
0.9.0a2
Fix
- Fixed version
0.9.0a2pip install --upgrade stigmem-node==0.9.0a2
Advisory
Also known as: CVE-2026-76244
stigmem-node's federation insecure transport settings may allow non-loopback cleartext federation
Impact
Stigmem nodes with federation enabled could be configured to run without mTLS outside loopback-only local development. In affected deployments, federation traffic may traverse the network without the intended transport protection. Impacted users are operators who enabled federation and explicitly disabled mTLS while binding the node to a non-loopback URL.
Patches
Patched in 0.9.0a2. The node now refuses this configuration unless insecure federation is limited to loopback-only local development.
Workarounds
Before upgrading, operators should enable mTLS for federation or ensure federation endpoints are bound only to loopback/private test environments and are not reachable by untrusted networks.
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
Critical Basis: The source's own band: CRITICAL
0, fixed 0.9.0a2 (ecosystem)0.9.0a2
0.9.0a2pip install --upgrade stigmem-node==0.9.0a2Fix 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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0