GHSA-wrr4-782v-jhwh: Neotoma Neotoma Has Tenant Isolation Gap Vulnerability

LOW
Share
CWE-201
Published
Advisory Summary

GHSA-wrr4-782v-jhwh is a LOW neotoma has tenant isolation gap vulnerability (CWE-201: Insertion of Sensitive Information Into Sent Data) affecting Neotoma libraries in the npm ecosystem. The issue involves neotoma has tenant isolation gap in relationship query endpoints. Remediation is available by upgrading affected packages to version 0.14.0.

GHSA-wrr4-782v-jhwh at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-wrr4-782v-jhwh
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-201: Insertion of Sensitive Information Into Sent Data
Affected Product Neotoma
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-wrr4-782v-jhwh

To remediate this vulnerability, upgrade all affected Neotoma dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

neotoma fixed: 0.14.0 
npm install neotoma@0.14.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls neotoma

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-wrr4-782v-jhwh, inspect your project dependencies using npm:

npm ls neotoma

Analyze the terminal output to locate any version of Neotoma in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.14.0), your application is affected.

Note: The npm ls neotoma command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-201: Insertion of Sensitive Information Into Sent Data, where the code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. In Neotoma, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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 1. A valid authentication token for the Neotoma instance (attacker must have a legitimate account on the same instance) 2. 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 1. Add `.eq("user_id", userId)` to all Supabase queries in both handlers 2. Validate entity ID inputs with `isNeotomaEntityId` before query construction 3. 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.

GHSA-wrr4-782v-jhwh Affected Neotoma Versions

1 component(s)
Fixed Versions:
0.14.0
Product / Package Ecosystem Affected Versions Fixed Version
neotoma
npm/neotoma
npm
≥ 0.13.0
< 0.14.0
0.14.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/markmhendrickson/neotoma/security/advisories/GHSA-wrr4-782v-jhwh
Neotoma Source Repository REPOSITORY
https://github.com/markmhendrickson/neotoma/issues/365
Neotoma Source Repository REPOSITORY
https://github.com/markmhendrickson/neotoma/issues/366
Neotoma Source Repository REPOSITORY
https://github.com/markmhendrickson/neotoma/issues/372
Neotoma Source Repository REPOSITORY
https://github.com/markmhendrickson/neotoma

Frequently Asked Questions

What is GHSA-wrr4-782v-jhwh?
GHSA-wrr4-782v-jhwh is a security vulnerability in Neotoma involving neotoma has tenant isolation gap in relationship query endpoints under CWE-201: Insertion of Sensitive Information Into Sent Data.
Which Neotoma versions are affected?
Affected versions include releases prior to 0.14.0 across affected packages: neotoma.
What version fixes GHSA-wrr4-782v-jhwh?
Upgrading to 0.14.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is neotoma affected?
Yes, neotoma is affected in releases prior to 0.14.0. Upgrade your dependency to 0.14.0 or later.
What CWE is associated with GHSA-wrr4-782v-jhwh?
GHSA-wrr4-782v-jhwh is classified under CWE-201: Insertion of Sensitive Information Into Sent Data (The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.).
How can I check npm dependencies for GHSA-wrr4-782v-jhwh?
Run the dependency tree command: 'npm ls neotoma'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wrr4-782v-jhwh",
  "modified" : "2026-06-25T17:46:49Z",
  "published" : "2026-06-25T17:46:49Z",
  "aliases" : [ ],
  "summary" : "neotoma has tenant isolation gap in relationship query endpoints",
  "details" : "## Summary\n\nThe `/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.\n\n## Affected code\n\n**`/list_relationships`** (`src/actions.ts`):\n- Calls `getAuthenticatedUserId` but does not apply `.eq(\"user_id\", userId)` to the relationships query\n- Uses `.or()` string interpolation for entity ID matching without input validation\n\n**`/retrieve_graph_neighborhood`** (`src/actions.ts`):\n- Same pattern: auth resolved, user ID not applied to query filter\n\n## Affected versions\n\nv0.13.0\n\n## Prerequisites\n\n1. A valid authentication token for the Neotoma instance (attacker must have a legitimate account on the same instance)\n2. A known entity ID belonging to another user (~96 bits of entropy — brute-force not practical)\n\nAn unauthenticated caller is rejected at the auth middleware layer. The gap requires a second user account on the instance.\n\n## Impact\n\nAn 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.\n\n## Severity\n\nLow under current conditions — no multi-tenant deployments exist. Escalates to Medium the moment two or more user accounts share an instance.\n\n## Remediation\n\n1. Add `.eq(\"user_id\", userId)` to all Supabase queries in both handlers\n2. Validate entity ID inputs with `isNeotomaEntityId` before query construction\n3. Replace `.or()` string interpolation with separate scoped `.eq()` calls\n\nFix tracked in #365 (list_relationships) and #366 (retrieve_graph_neighborhood). Gate gap tracked in #372.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "neotoma"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.13.0"
      }, {
        "fixed" : "0.14.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/markmhendrickson/neotoma/security/advisories/GHSA-wrr4-782v-jhwh"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/markmhendrickson/neotoma/issues/365"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/markmhendrickson/neotoma/issues/366"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/markmhendrickson/neotoma/issues/372"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/markmhendrickson/neotoma"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-201" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-25T17:46:49Z",
    "nvd_published_at" : null
  }
}