dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-44830

HIGH · 8.7 CVSS v4.0 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
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
Nocturne Memory is a lightweight, rollbackable, and visual Long-Term Memory Server for MCP Agents. Prior to 2.4.1, when API_TOKEN is unset or empty, the BearerTokenAuthMiddleware bypasses authentication for all HTTP requests. Combined with the default 0.0.0.0 host binding and CORS allow_origins=["*"], operators following the Docker setup without explicitly setting API_TOKEN expose the full Knowledge-Graph read/write API to any LAN-reachable client. An attacker on the same network can read, write, or delete all memory entries — including system://boot and core://* URIs that auto-load into downstream agent sessions, enabling persistent prompt-injection. This vulnerability is fixed in 2.4.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

Nocturne Memory versions prior to 2.4.1 have an authentication bypass in BearerTokenAuthMiddleware when API_TOKEN is unset or empty. Combined with default 0.0.0.0 binding and CORS allow_origins=['*'], this exposes the entire Knowledge-Graph read/write API to any LAN-accessible attacker, allowing read/write/delete of all memory entries including boot sequences and core URIs for persistent prompt injection.

MitigationUpgrade to version 2.4.1 or later and ensure API_TOKEN environment variable is explicitly set to a strong value; additionally restrict host binding to localhost or trusted networks and narrow CORS allow_origins.

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
Adjacent
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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. Check Nocturne Memory version
    Run 'nocturne --version' or check the installed package version via pip/pip3 list | grep -i nocturne
    Affected if Version is prior to 2.4.1
  2. Verify API_TOKEN environment variable is set
    Run 'echo $API_TOKEN' in the shell where Nocturne runs; if empty or unset, the vulnerability applies
    Affected if API_TOKEN environment variable is unset or empty string
  3. Inspect server binding configuration
    Check Nocturne configuration files or startup logs for the host binding address; default 0.0.0.0 exposes to all network interfaces
    Affected if Server binds to 0.0.0.0 rather than localhost or a trusted IP
  4. Review CORS allow_origins setting
    Check configuration files or code for CORS settings; look for allow_origins=['*'] or similar wildcard configuration
    Affected if CORS allow_origins is set to wildcard '*' or includes untrusted origins

User is affected if Nocturne Memory version is below 2.4.1 AND API_TOKEN is unset/empty, especially when combined with default 0.0.0.0 binding and permissive CORS settings.

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 2.4.1 or later and ensure API_TOKEN environment variable is explicitly set to a strong value; additionally restrict host binding to localhost or trusted networks and narrow CORS allow_origins.

Recommended fix High confidence

2.4.1

  1. Check the currently running Nocturne Memory version (e.g., docker ps or check the container tag)
  2. Backup any existing memory data and configuration files before upgrading
  3. Pull the updated Nocturne Memory image with version 2.4.1 (e.g., docker pull nocturne-memory:2.4.1 or using your specific image name and tag)
  4. Stop and remove the existing container
  5. Deploy a new container using the 2.4.1 image with the same configuration used previously
  6. Verify the container started successfully and is running version 2.4.1
  7. Test that the API now requires authentication (requests without a valid Bearer token should be rejected)

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44830 — 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-44830 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