Summary
stigmem-node: Auth-disabled deployments may grant broad anonymous access outside loopback
Workarounds
Before upgrading, keep authentication enabled for all non-local deployments and do not expose nodes with authentication disabled to untrusted networks.
Upgrade
Upgrade to the patched release:
pip install --upgrade --pre stigmem-node
If developers install through the Stigmem meta-package instead, they should use the matching extra for their deployments, for example:
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
Impact
Stigmem nodes configured with authentication disabled could grant the anonymous identity broad read/write/federation capabilities if exposed outside a loopback-only local development environment. Impacted users are operators who intentionally disabled authentication while binding the node to a non-loopback URL.
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Patched in 0.9.0a2. The node now refuses unauthenticated operation outside loopback-only local development.
Frequently Asked Questions
- What is GHSA-FP6W-8WPG-74G5? GHSA-FP6W-8WPG-74G5 is a critical-severity missing authorization vulnerability in stigmem-node (pip), affecting versions < 0.9.0a2. It is fixed in 0.9.0a2. The application does not perform an authorization check before performing a sensitive operation.
- Which versions of stigmem-node are affected by GHSA-FP6W-8WPG-74G5? stigmem-node (pip) versions < 0.9.0a2 is affected.
- Is there a fix for GHSA-FP6W-8WPG-74G5? Yes. GHSA-FP6W-8WPG-74G5 is fixed in 0.9.0a2. Upgrade to this version or later.
- Is GHSA-FP6W-8WPG-74G5 exploitable, and should I be worried? Whether GHSA-FP6W-8WPG-74G5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-FP6W-8WPG-74G5 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-FP6W-8WPG-74G5? Upgrade
stigmem-nodeto 0.9.0a2 or later.