# CVE-2026-44830: Empty API_TOKEN disables authentication on network-reachable HTTP/SSE transport

> Attackers on the same network can read, write, or delete memory entries if the API token is unset, enabling persistent prompt injection.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-crr4-xrj9-ww8g

## What is CVE-2026-44830?

CVE-2026-44830 is a high-severity authentication bypass vulnerability in Dataojitori nocturne_memory, published on 27 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-44830?


## How do I fix CVE-2026-44830?

No fix has been published for CVE-2026-44830 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44830 being exploited?

There is no known exploitation of CVE-2026-44830 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44830 and fix it if it is affected.

What it is: CVE-2026-44830 is a high-severity authentication bypass vulnerability in Dataojitori nocturne_memory, published on 27 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44830 in the wild and no public exploit code.

Affected product: Dataojitori nocturne_memory. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44830/ (Markdown: https://insights.sbomify.com/CVE-2026-44830/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44830
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44830
- OSV: https://osv.dev/vulnerability/CVE-2026-44830

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44830/
Summaries are generated and may contain mistakes; the official description above is the record.