How severe is GHSA-wrr4-782v-jhwh?

No CVSS score has been assigned to GHSA-wrr4-782v-jhwh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wrr4-782v-jhwh?

GHSA-wrr4-782v-jhwh affects the following packages: neotoma (npm). Ecosystems affected: npm.

How do I fix GHSA-wrr4-782v-jhwh?

Update neotoma to 0.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wrr4-782v-jhwh is resolved across your whole dependency graph.

How do I detect GHSA-wrr4-782v-jhwh in my npm dependencies?

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

How do I mitigate GHSA-wrr4-782v-jhwh 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-wrr4-782v-jhwh actively exploited in the wild?

No public exploit code has been indexed for GHSA-wrr4-782v-jhwh 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.

When was GHSA-wrr4-782v-jhwh published, and has it been updated?

GHSA-wrr4-782v-jhwh was published on June 25, 2026 and was last updated on June 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

neotoma has tenant isolation gap in relationship query endpointsGHSA-wrr4-782v-jhwh

GHSA-wrr4-782v-jhwh is a security vulnerability in neotoma. A fix is available for neotoma — see the affected versions and patch details below.

Published

Jun 25, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 25, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

neotomanpm

145downloads / week

Description

Summary

The /list_relationships and /retrieve_graph_neighborhood endpoints call getAuthenticatedUserId (confirming a valid session exists) but do not pass the resolved user ID into the Supabase query as an .eq("user_id", userId) filter. As a result, queries return rows from all users rather than scoping to the authenticated caller's data.

Affected code

/list_relationships (src/actions.ts):

Calls getAuthenticatedUserId but does not apply .eq("user_id", userId) to the relationships query
Uses .or() string interpolation for entity ID matching without input validation

/retrieve_graph_neighborhood (src/actions.ts):

Same pattern: auth resolved, user ID not applied to query filter

Affected versions

v0.13.0

Prerequisites

A valid authentication token for the Neotoma instance (attacker must have a legitimate account on the same instance)
A known entity ID belonging to another user (~96 bits of entropy — brute-force not practical)

An unauthenticated caller is rejected at the auth middleware layer. The gap requires a second user account on the instance.

Impact

An authenticated user with a known cross-user entity ID can retrieve relationship edges and graph neighborhood data belonging to another user. No write capability is exposed.

Severity

Low under current conditions — no multi-tenant deployments exist. Escalates to Medium the moment two or more user accounts share an instance.

Remediation

Add .eq("user_id", userId) to all Supabase queries in both handlers
Validate entity ID inputs with isNeotomaEntityId before query construction
Replace .or() string interpolation with separate scoped .eq() calls

Fix tracked in #365 (list_relationships) and #366 (retrieve_graph_neighborhood). Gate gap tracked in #372.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`neotoma`	≥ 0.13.0&&< 0.14.0	0.14.0`npm install neotoma@0.14.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neotoma, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update neotoma to 0.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wrr4-782v-jhwh 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 The `/list_relationships` and `/retrieve_graph_neighborhood` endpoints call `getAuthenticatedUserId` (confirming a valid session exists) but do not pass the resolved user ID into the Supabase query as an `.eq("user_id", userId)` filter. As a result, queries return rows from all users rather than scoping to the authenticated caller's data. ## Affected code **`/list_relationships`** (`src/actions.ts`): - Calls `getAuthenticatedUserId` but does not apply `.eq("user_id", userId)` to the relationships query - Uses `.or()` string interpolation for entity ID matching without input valid

O3 Security · Impact-Aware SCA

Is GHSA-wrr4-782v-jhwh in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works