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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 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
- 31 Oct 2026, 14:39 UTC First seen by agentprime
- 31 Oct 2026, 14:39 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-xh5j-xjfq-qvvx
- OSV: GHSA-xh5j-xjfq-qvvx
- github.com/eidetic-labs/stigmem/security/advisories/GHSA-xh5j-xjfq-qvvx
- github.com/eidetic-labs/stigmem
- github.com/eidetic-labs/stigmem/blob/v0.9.0a2/CHANGELOG.md#L14-L35
- github.com/eidetic-labs/stigmem/blob/v0.9.0a2/SECURITY.md
- github.com/eidetic-labs/stigmem/releases/tag/v0.9.0a2