# stigmem-node's federation peer registration lacked explicit out-of-band approval Advisory record · `GHSA-9vp8-3hmv-8fgh` - **Identifiers:** `GHSA-9vp8-3hmv-8fgh` · `CVE-2026-76242` - **State:** Confirmed - **Severity:** CVSS 9.1 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-295](https://cwe.mitre.org/data/definitions/295.html) · [CWE-345](https://cwe.mitre.org/data/definitions/345.html) - **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md) · [CWE-345](https://agentprime.io/advisories/tag/cwe-345.md) - **Published:** 29 May 2026 - **Updated:** 20 Aug 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 29 May 2026, 22:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 9.1: 9.0 or more. How we decide what’s critical: ## Affected packages - `stigmem-node` (PyPI): affected `<0.9.0a2`; fixed in `0.9.0a2` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > stigmem-node versions before 0.9.0a2 accept federation peer key material during registration without a separate administrator approval step based on an out-of-band fingerprint check. An attacker who can intercept or misdirect initial peer registration on the network could have a peer accepted. Upgrade to stigmem-node 0.9.0a2, which requires administrator approval using the expected fingerprint before peer tokens are accepted; until then, restrict peer registration endpoints to trusted administrative networks. 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 - 9.1 Critical, CVSS 4.0: `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`, from CNA (VulnCheck) - **CISA KEV:** Not listed. - **EPSS:** 0.0035, the 28th percentile, on 10 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](https://osv.dev/vulnerability/GHSA-9vp8-3hmv-8fgh) ## Sources - [GitHub Advisory Database: GHSA-9vp8-3hmv-8fgh](https://github.com/advisories/GHSA-9vp8-3hmv-8fgh) - [OSV: GHSA-9vp8-3hmv-8fgh](https://osv.dev/vulnerability/GHSA-9vp8-3hmv-8fgh) - - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .