Advisory record · GHSA-xh5j-xjfq-qvvx

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

CVSS 7.1 HighEPSS 0.0024 · 14th percentile

Published by the GitHub Advisory Database at 29 May 2026, 22:14 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
stigmem-nodePyPI<0.9.0a20.9.0a2
Identifiers
GHSA-xh5j-xjfq-qvvx · CVE-2026-76245
Weakness (CWE)
CWE-345
Published
29 May 2026
Updated
20 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The stigmem-node package, versions before 0.9.0a2, has a timestamp handling mismatch in federation peer-token validation that can cause valid peer tokens to be treated as expired. An attacker is not described as needing any specific access; the impact is on availability and reliability of authenticated federation flows. Upgrade to stigmem-node 0.9.0a2. Before upgrading, avoid mixing peer-token minting paths and limit federation use to tightly controlled peers.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.1 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0024, the 14th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:39 UTC First seen by agentprime
  2. 31 Oct 2026, 14:39 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.