How severe is GHSA-jmfc-hfjq-pxcp?

No CVSS score has been assigned to GHSA-jmfc-hfjq-pxcp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jmfc-hfjq-pxcp?

GHSA-jmfc-hfjq-pxcp affects the following packages: stigmem-node (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-jmfc-hfjq-pxcp?

Update stigmem-node to 0.9.0a2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jmfc-hfjq-pxcp is resolved across your whole dependency graph.

How do I detect GHSA-jmfc-hfjq-pxcp in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for stigmem-node, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-jmfc-hfjq-pxcp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-jmfc-hfjq-pxcp actively exploited in the wild?

No public exploit code has been indexed for GHSA-jmfc-hfjq-pxcp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-jmfc-hfjq-pxcp?

GHSA-jmfc-hfjq-pxcp has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-jmfc-hfjq-pxcp?

GHSA-jmfc-hfjq-pxcp is classified as CWE-319 (CWE-319). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jmfc-hfjq-pxcp published, and has it been updated?

GHSA-jmfc-hfjq-pxcp was published on May 29, 2026 and was last updated on August 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

stigmem-node's federation insecure transport settings may allow non-loopback cleartext federationGHSA-jmfc-hfjq-pxcp

GHSA-jmfc-hfjq-pxcp is a CWE-319 vulnerability in stigmem-node. A fix is available for stigmem-node — see the affected versions and patch details below.

Also known asCVE-2026-76244

Published

May 29, 2026

Updated

Aug 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-jmfc-hfjq-pxcp.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍stigmem-node

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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:

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:

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`stigmem-node`	all versions	0.9.0a2`pip install --upgrade 'stigmem-node==0.9.0a2'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for stigmem-node, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update stigmem-node to 0.9.0a2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jmfc-hfjq-pxcp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-jmfc-hfjq-pxcp in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

stigmem-node's federation insecure transport settings may allow non-loopback cleartext federationGHSA-jmfc-hfjq-pxcp

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Patches

Workarounds

Upgrade

Resources

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-jmfc-hfjq-pxcp in your dependencies?