GitHub Advisoryadvisory · npm

GHSA-5cvp-p7p4-mcx9 Neotoma: Unauthenticated Inspector/API access via reverse-proxy loopback auth bypass

MEDIUM Published 2026-05-18 Modified 2026-06-09 Official page ↗
Aliases
CVE-2026-45577
Ecosystem
npm
Packages
neotoma
Severity
Moderate
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Weaknesses
CWE-288, CWE-306
Reviewed
2026-05-18

Affected packages

• npm neotoma: >= 0.6.0, < 0.11.1 → fixed in 0.11.1

Description

Neotoma versions starting at v0.6.0 can treat public reverse-proxied requests as local when the app receives them over a loopback socket and no Bearer token is present. In affected deployments, the REST auth middleware can resolve unauthenticated requests as the local development user, making the hosted Inspector and related API surface reachable without credentials. Impact: unauthorized access to production data exposed through the Inspector/API on affected deployments. Affected condition: a public deployment behind a reverse proxy or same-host tunnel that forwards traffic to the Node process over loopback. Remediation implemented on the main branch: local-request detection now fails closed in production unless loopback trust is explicitly enabled, and forwarded public clients remain remote. Patched release version is pending; this draft will be updated once the fix is released.

Related

Alias · CVE (1)

  • CVE-2026-45577 Neotoma provides versioned records that persist across agent runs. vulnerability

Weakness · CWE (2)

  • CWE-288 Authentication Bypass Using an Alternate Path or Channel weakness
  • CWE-306 Missing Authentication for Critical Functionality weakness

References