How severe is GHSA-xhv3-q4xx-349r?

No CVSS score has been assigned to GHSA-xhv3-q4xx-349r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xhv3-q4xx-349r?

GHSA-xhv3-q4xx-349r affects the following packages: stigmem-node (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-xhv3-q4xx-349r?

Update stigmem-node to 0.9.0a12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xhv3-q4xx-349r is resolved across your whole dependency graph.

How do I detect GHSA-xhv3-q4xx-349r 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-xhv3-q4xx-349r 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-xhv3-q4xx-349r actively exploited in the wild?

No public exploit code has been indexed for GHSA-xhv3-q4xx-349r 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-xhv3-q4xx-349r?

GHSA-xhv3-q4xx-349r has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th 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-xhv3-q4xx-349r?

GHSA-xhv3-q4xx-349r is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xhv3-q4xx-349r published, and has it been updated?

GHSA-xhv3-q4xx-349r was published on June 19, 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

stistigmem-node: quarantine review surface exposes and mutates other tenants' quarantined facts (cross-tenant BOLA)GHSA-xhv3-q4xx-349r

Fix: eidetic-labs/stigmem#728

GHSA-xhv3-q4xx-349r is a CWE-639 vulnerability in stigmem-node. A fix is available for stigmem-node — see the affected versions and patch details below.

Also known asCVE-2026-76237

Published

Jun 19, 2026

Updated

Aug 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 30, 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-xhv3-q4xx-349r.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs30th percentile — riskier than 30% 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

Summary

On a multi-tenant stigmem node, a tenant administrator could list, read, and admit or reject quarantined facts belonging to other tenants. The list/count queries and _get_quarantined_fact in routes/quarantine.py lacked an f.tenant_id = identity.tenant_id predicate, and the garden lookup was not tenant-scoped — reached via the /v1/quarantine list and admit/reject endpoints.

Impact

Cross-tenant confidentiality (reading another tenant's quarantined content) and cross-tenant integrity (moderating — admitting or rejecting — another tenant's facts), gated only by a plain tenant write capability rather than a node-level admin authority.

Affected configurations

This is a cross-tenant break. It is exploitable only on deployments running the opt-in stigmem-plugin-multi-tenant (multiple tenants on one node). A default single-tenant node has only tenant="default" — there is no second tenant to cross — so it is not exploitable on default deployments. The rating is HIGH for the multi-tenant deployments the plugin exists to isolate.

Patches

Fixed in 0.9.0a12 (PR #728): AND f.tenant_id = identity.tenant_id was added to the list/count queries and _get_quarantined_fact; the garden lookup is now tenant-scoped; and any genuinely cross-tenant moderation is gated behind can_admin_federation() (node superadmin), not a tenant write capability. A tenant-B admin can no longer list, admit, or reject tenant-A's quarantined facts.

Workarounds

None other than upgrading to 0.9.0a12. Single-tenant deployments are unaffected.

Affected Packages

1 total 1 fixed

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

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.0a12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xhv3-q4xx-349r 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

### Summary On a multi-tenant stigmem node, a tenant administrator could list, read, and **admit or reject** quarantined facts belonging to **other** tenants. The list/count queries and `_get_quarantined_fact` in `routes/quarantine.py` lacked an `f.tenant_id = identity.tenant_id` predicate, and the garden lookup was not tenant-scoped — reached via the `/v1/quarantine` list and admit/reject endpoints. ### Impact Cross-tenant confidentiality (reading another tenant's quarantined content) and cross-tenant integrity (moderating — admitting or rejecting — another tenant's facts), gated only by a p

O3 Security · Impact-Aware SCA

Is GHSA-xhv3-q4xx-349r in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works