GHSA-xh5j-xjfq-qvvx stigmem-node's federation peer token timestamp validation may reject valid peer tokens

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

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: ```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