GHSA-xh5j-xjfq-qvvx: Stigmem node Stigmem-node's Federation Peer Token Timestamp Vulnerability

HIGH
CWE-345
Published
Advisory Summary

GHSA-xh5j-xjfq-qvvx is a HIGH stigmem-node's federation peer token timestamp vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting Stigmem node libraries in the PyPI ecosystem. The issue involves stigmem-node's federation peer token timestamp validation may reject valid peer tokens. Remediation is available by upgrading affected packages to version 0.9.0a2.

GHSA-xh5j-xjfq-qvvx at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-xh5j-xjfq-qvvx
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
Affected Product Stigmem node
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix GHSA-xh5j-xjfq-qvvx

To remediate this vulnerability, upgrade all affected Stigmem node dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

stigmem-node fixed: 0.9.0a2
pip install stigmem-node>=0.9.0a2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show stigmem-node

How to Check if You Are Affected

To determine whether your Python environment is affected by GHSA-xh5j-xjfq-qvvx, inspect your installed packages using pip:

pip show stigmem-node

Analyze the terminal output to locate any version of Stigmem node in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.9.0a2), your application is affected.

Note: The pip show stigmem-node command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In Stigmem node, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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

GHSA-xh5j-xjfq-qvvx Affected Stigmem node Versions

1 component(s)
Fixed Versions:
0.9.0a2
Product / Package Ecosystem Affected Versions Fixed Version
stigmem-node
PyPI
< 0.9.0a2
0.9.0a2

References

Frequently Asked Questions

What is GHSA-xh5j-xjfq-qvvx?
GHSA-xh5j-xjfq-qvvx is a security vulnerability in Stigmem node involving stigmem-node's federation peer token timestamp validation may reject valid peer tokens under CWE-345: Insufficient Verification of Data Authenticity.
Which Stigmem node versions are affected?
Affected versions include releases prior to 0.9.0a2 across affected packages: stigmem-node.
What version fixes GHSA-xh5j-xjfq-qvvx?
Upgrading to 0.9.0a2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is stigmem-node affected?
Yes, stigmem-node is affected in releases prior to 0.9.0a2. Upgrade your dependency to 0.9.0a2 or later.
What CWE is associated with GHSA-xh5j-xjfq-qvvx?
GHSA-xh5j-xjfq-qvvx is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check PyPI dependencies for GHSA-xh5j-xjfq-qvvx?
Run the dependency tree command: 'pip show stigmem-node'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xh5j-xjfq-qvvx",
  "modified" : "2026-05-29T22:14:34Z",
  "published" : "2026-05-29T22:14:34Z",
  "aliases" : [ ],
  "summary" : "stigmem-node's federation peer token timestamp validation may reject valid peer tokens",
  "details" : "### Impact\nA 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.\n\n### Patches\nPatched in 0.9.0a2. Federation peer-token timestamp handling now uses the canonical millisecond-based validation path and is covered by regression tests.\n\n### Workarounds\nBefore upgrading, avoid mixed peer-token minting paths and restrict federation use to tightly controlled peers.\n\n### Upgrade\nUpgrade to the patched release:\n\n```bash\npip install --upgrade --pre stigmem-node\n```\n\nIf developers install through the Stigmem meta-package instead, they should use the matching extra for deployments, for example:\n\n```bash\npip install --upgrade --pre 'stigmem[node]'\n```\n\n### Resources\n- Release: https://github.com/eidetic-labs/stigmem/releases/tag/v0.9.0a2\n- Changelog: https://github.com/eidetic-labs/stigmem/blob/v0.9.0a2/CHANGELOG.md#L14-L35\n- Security policy and posture: https://github.com/eidetic-labs/stigmem/blob/v0.9.0a2/SECURITY.md",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "stigmem-node"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.9.0a2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/eidetic-labs/stigmem/security/advisories/GHSA-xh5j-xjfq-qvvx"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/eidetic-labs/stigmem"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/eidetic-labs/stigmem/blob/v0.9.0a2/CHANGELOG.md#L14-L35"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/eidetic-labs/stigmem/blob/v0.9.0a2/SECURITY.md"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/eidetic-labs/stigmem/releases/tag/v0.9.0a2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-345" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-29T22:14:34Z",
    "nvd_published_at" : null
  }
}