dbcve.org
CWE-288Weakness · CWE-288

CVE-2026-45577

MEDIUM · 6.9 CVSS v4.0 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Neotoma provides versioned records that persist across agent runs. From 0.6.0 to before 0.11.1, Neotoma 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. This vulnerability is fixed in 0.11.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Neotoma versions 0.6.0 through 0.11.0 have an authentication bypass vulnerability where requests received over loopback sockets without a Bearer token are incorrectly treated as coming from the local development user. This allows unauthenticated access to the Inspector and API endpoints when requests are routed through a reverse proxy.

MitigationUpgrade to version 0.11.1 or later. If immediate upgrade is not possible, ensure the reverse proxy enforces authentication before forwarding requests to Neotoma and review authentication configuration to not trust loopback requests without credentials.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Neotoma version
    Locate the Neotoma installation and retrieve its version number using the package manager, version flag (e.g., neotoma --version), or by inspecting the installed package metadata. Compare the version to the affected range 0.6.0 through 0.11.0.
    Affected if The installed version falls within 0.6.0 to 0.11.0 inclusive.
  2. Determine if Neotoma is exposed via reverse proxy
    Review the deployment architecture. Inspect reverse proxy configuration files (such as nginx, Apache, or cloud proxy settings) to verify whether incoming traffic to Neotoma passes through a reverse proxy before reaching the application loopback socket.
    Affected if A reverse proxy forwards requests to Neotoma running on a loopback interface.
  3. Verify authentication enforcement on Inspector UI
    Attempt to access the Inspector UI endpoint (typically at /inspector or similar) by sending a request without a Bearer token. Observe whether the UI loads without requiring authentication.
    Affected if The Inspector UI loads successfully without a Bearer token when accessed through the reverse proxy.
  4. Check API endpoint authentication
    Send a request to one or more REST API endpoints without a Bearer token header. Verify whether API responses are returned with elevated privileges or sensitive data that should require authentication.
    Affected if API endpoints return successful responses with elevated access without providing a Bearer token.

If Neotoma version is between 0.6.0 and 0.11.0 and the application is accessible through a reverse proxy without enforced Bearer token authentication, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 0.11.1 or later. If immediate upgrade is not possible, ensure the reverse proxy enforces authentication before forwarding requests to Neotoma and review authentication configuration to not trust loopback requests without credentials.

Recommended fix High confidence

0.11.1 or later

  1. Identify the current installed version of Neotoma by checking project dependencies or package manager
  2. If running version 0.6.0 through 0.11.0, plan for upgrade to version 0.11.1 or later
  3. Update the dependency version in your project's package configuration (e.g., package.json, requirements.txt, or equivalent)
  4. Run package manager update/install command to fetch the fixed version
  5. Restart the Neotoma service to apply the updated package
  6. Verify the upgrade was successful by checking the running version
  7. Test that authentication is now properly enforced on the Inspector and related API endpoints
Caveat Review release notes between your current version and 0.11.1 for any breaking changes or migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45577 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45577 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data