Advisory record · GHSA-jmfc-hfjq-pxcp

stigmem-node's federation insecure transport settings may allow non-loopback cleartext federation

CVSS 9.1 CriticalCriticalEPSS 0.0027 · 19th percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 29 May 2026, 22:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
stigmem-nodePyPI<0.9.0a20.9.0a2
Identifiers
GHSA-jmfc-hfjq-pxcp · CVE-2026-76244
Weakness (CWE)
CWE-319 · CWE-489
Published
29 May 2026
Updated
20 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

stigmem-node versions before 0.9.0a2 are affected. A node with federation enabled and mTLS explicitly disabled, bound to a non-loopback URL, may send federation traffic over the network without transport protection, so an attacker able to observe that network traffic could read it. Upgrade to stigmem-node 0.9.0a2, which refuses this configuration unless insecure federation is limited to loopback-only local development. Until then, enable mTLS for federation or make sure federation endpoints are reachable only from loopback or private test environments.

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

ScoreRatingCVSSVectorSource
9.1 Critical 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0027, the 19th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:39 UTC First seen by agentprime
  2. 31 Oct 2026, 14:39 UTC Confirmed by OSV

Sources

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.