GHSA-jmfc-hfjq-pxcp: Stigmem node Stigmem-node's Federation Insecure Transport Settings Vulnerability

CRITICAL
Share
CWE-489 CWE-319
Published
Advisory Summary

GHSA-jmfc-hfjq-pxcp is a CRITICAL stigmem-node's federation insecure transport settings vulnerability (CWE-489: Active Debug Code) affecting Stigmem node libraries in the PyPI ecosystem. The issue involves stigmem-node's federation insecure transport settings may allow non-loopback cleartext federation. Remediation is available by upgrading affected packages to version 0.9.0a2.

GHSA-jmfc-hfjq-pxcp at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-jmfc-hfjq-pxcp
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-489: Active Debug Code
Affected Product Stigmem node
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix GHSA-jmfc-hfjq-pxcp

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-jmfc-hfjq-pxcp, 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-489: Active Debug Code, where the product is released with debugging code still enabled or active. 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 Stigmem nodes with federation enabled could be configured to run without mTLS outside loopback-only local development. In affected deployments, federation traffic may traverse the network without the intended transport protection. Impacted users are operators who enabled federation and explicitly disabled mTLS while binding the node to a non-loopback URL. ### Patches Patched in 0.9.0a2. The node now refuses this configuration unless insecure federation is limited to loopback-only local development. ### Workarounds Before upgrading, operators should enable mTLS for federation or ensure federation endpoints are bound only to loopback/private test environments and are not reachable by untrusted networks. ### 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-jmfc-hfjq-pxcp Affected Stigmem node Versions

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

References

GitHub Advisory / Wiki ADVISORY
https://github.com/eidetic-labs/stigmem/security/advisories/GHSA-jmfc-hfjq-pxcp
Stigmem node Source Repository REPOSITORY
https://github.com/eidetic-labs/stigmem

Frequently Asked Questions

What is GHSA-jmfc-hfjq-pxcp?
GHSA-jmfc-hfjq-pxcp is a security vulnerability in Stigmem node involving stigmem-node's federation insecure transport settings may allow non-loopback cleartext federation under CWE-489: Active Debug Code.
Which Stigmem node versions are affected?
Affected versions include releases prior to 0.9.0a2 across affected packages: stigmem-node.
What version fixes GHSA-jmfc-hfjq-pxcp?
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-jmfc-hfjq-pxcp?
GHSA-jmfc-hfjq-pxcp is classified under CWE-489: Active Debug Code (The product is released with debugging code still enabled or active.).
How can I check PyPI dependencies for GHSA-jmfc-hfjq-pxcp?
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
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jmfc-hfjq-pxcp",
  "modified" : "2026-05-29T22:16:27Z",
  "published" : "2026-05-29T22:16:27Z",
  "aliases" : [ ],
  "summary" : "stigmem-node's federation insecure transport settings may allow non-loopback cleartext federation",
  "details" : "### Impact\nStigmem nodes with federation enabled could be configured to run without mTLS outside loopback-only local development. In affected deployments, federation traffic may traverse the network without the intended transport protection. Impacted users are operators who enabled federation and explicitly disabled mTLS while binding the node to a non-loopback URL.\n\n### Patches\nPatched in 0.9.0a2. The node now refuses this configuration unless insecure federation is limited to loopback-only local development.\n\n### Workarounds\nBefore upgrading, operators should enable mTLS for federation or ensure federation endpoints are bound only to loopback/private test environments and are not reachable by untrusted networks.\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: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-jmfc-hfjq-pxcp"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/eidetic-labs/stigmem"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-319", "CWE-489" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-29T22:16:27Z",
    "nvd_published_at" : null
  }
}