GHSA-wrr4-782v-jhwh: neotoma has tenant isolation gap in relationship query endpoints
Summary The /listrelationships and /retrievegraphneighborhood endpoints call getAuthenticatedUserId (confirming a valid session exists) but do not pass the resolved user ID into the Supabase query as an .eq("userid", userId) filter. As a result, queries return rows from all users rather than scoping to the authenticated caller's data.
Published Jun 25, 2026
Affected packages
neotoma
- Ecosystem
- npm
- Affected
- >= 0.13.0, < 0.14.0
- Fixed in
- 0.14.0
- Check
npm ls neotoma
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
getAuthenticatedUserIdbut 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
isNeotomaEntityIdbefore 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.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
