Advisory

GHSA-xh5j-xjfq-qvvx

Also known as: CVE-2026-76245

Summary

stigmem-node's federation peer token timestamp validation may reject valid peer tokens

Details

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

  • 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:14 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