GHSA-9vp8-3hmv-8fgh: Stigmem node Stigmem-node's Federation Peer Registration Lacked Vulnerability

CRITICAL
CWE-295 CWE-345
Published
Advisory Summary

GHSA-9vp8-3hmv-8fgh is a CRITICAL stigmem-node's federation peer registration lacked vulnerability (CWE-295: Improper Certificate Validation) affecting Stigmem node libraries in the PyPI ecosystem. The issue involves stigmem-node's federation peer registration lacked explicit out-of-band approval. Remediation is available by upgrading affected packages to version 0.9.0a2.

GHSA-9vp8-3hmv-8fgh at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-9vp8-3hmv-8fgh
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-295: Improper Certificate Validation
Affected Product Stigmem node
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix GHSA-9vp8-3hmv-8fgh

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-9vp8-3hmv-8fgh, 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-295: Improper Certificate Validation, where the product does not validate, or incorrectly validates, a certificate. 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 Federation peer registration accepted peer key material during registration without a separate administrator approval step based on an out-of-band fingerprint check. Impacted deployments are nodes that accept federation peer registration across a network where initial registration could be intercepted or misdirected. ### Patches Patched in 0.9.0a2. Peer registration now uses a pending approval flow, and peer tokens are not accepted until an administrator approves the peer using the expected fingerprint. ### Workarounds Before upgrading, restrict peer registration endpoints to trusted administrative networks and verify peer public-key fingerprints out of band before allowing federation traffic. ### 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-9vp8-3hmv-8fgh 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-9vp8-3hmv-8fgh?
GHSA-9vp8-3hmv-8fgh is a security vulnerability in Stigmem node involving stigmem-node's federation peer registration lacked explicit out-of-band approval under CWE-295: Improper Certificate Validation.
Which Stigmem node versions are affected?
Affected versions include releases prior to 0.9.0a2 across affected packages: stigmem-node.
What version fixes GHSA-9vp8-3hmv-8fgh?
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-9vp8-3hmv-8fgh?
GHSA-9vp8-3hmv-8fgh is classified under CWE-295: Improper Certificate Validation (The product does not validate, or incorrectly validates, a certificate.).
How can I check PyPI dependencies for GHSA-9vp8-3hmv-8fgh?
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-9vp8-3hmv-8fgh",
  "modified" : "2026-05-29T22:18:19Z",
  "published" : "2026-05-29T22:18:19Z",
  "aliases" : [ ],
  "summary" : "stigmem-node's federation peer registration lacked explicit out-of-band approval",
  "details" : "### Impact\nFederation peer registration accepted peer key material during registration without a separate administrator approval step based on an out-of-band fingerprint check. Impacted deployments are nodes that accept federation peer registration across a network where initial registration could be intercepted or misdirected.\n\n### Patches\nPatched in 0.9.0a2. Peer registration now uses a pending approval flow, and peer tokens are not accepted until an administrator approves the peer using the expected fingerprint.\n\n### Workarounds\nBefore upgrading, restrict peer registration endpoints to trusted administrative networks and verify peer public-key fingerprints out of band before allowing federation traffic.\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:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/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-9vp8-3hmv-8fgh"
  }, {
    "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-295", "CWE-345" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-29T22:18:19Z",
    "nvd_published_at" : null
  }
}