criticalVulnerability

GHSA-9vp8-3hmv-8fgh

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

Properties

ghsa_id
GHSA-9vp8-3hmv-8fgh
severity
critical
summary
stigmem-node's federation peer registration lacked explicit out-of-band approval
cve_id
GHSA-9vp8-3hmv-8fgh
is_ghsa_only
true
ghsa_published
2026-05-29T22:18:19Z
source_url
https://github.com/advisories/GHSA-9vp8-3hmv-8fgh
ghsa_updated
2026-05-29T22:18:21Z

Related Entities (5)

VULNERABLE_TO (1)

[Software]pip/stigmem-node

AFFECTS (1)

[Software]pip/stigmem-node

HAS_WEAKNESS (2)

[Weakness]Improper Certificate Validation
[Weakness]Insufficient Verification of Data Authenticity

REPORTED_BY (1)

[Source]GitHub Advisory Database

Explore deeper with Ninja Signal's threat intelligence graph

GHSA-9vp8-3hmv-8fgh — Ninja Signal Threat Intelligence | Ninja Signal