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-76245
stigmem-node's federation peer token timestamp validation may reject valid peer tokens
Impact
A mismatch in federation peer-token timestamp handling could cause valid peer tokens to be treated as expired. Impacted deployments are Stigmem nodes using federation peer authentication paths from affected versions. The primary impact is availability and reliability of authenticated federation flows.
Patches
Patched in 0.9.0a2. Federation peer-token timestamp handling now uses the canonical millisecond-based validation path and is covered by regression tests.
Workarounds
Before upgrading, avoid mixed peer-token minting paths and restrict federation use to tightly controlled peers.
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
High Basis: The source's own band: HIGH
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