CVE-2026-31245
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 · uneditedThe mem0 1.0.0 server lacks authentication and authorization controls for its memory creation API endpoint (POST /memories). The endpoint allows unauthenticated users to submit arbitrary memory records without verifying their identity or permissions. A remote attacker can exploit this by sending unauthenticated POST requests to create malicious or spoofed memory entries in the database, leading to unauthorized data injection and potential data pollution.
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 confidenceThe mem0 1.0.0 server exposes a POST /memories API endpoint without any authentication or authorization checks. This allows any remote attacker to send unauthenticated HTTP POST requests and inject arbitrary memory records into the database, enabling data pollution and potential injection of malicious content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.0CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm mem0 server is runningCheck if the mem0 server process is active. On Linux: `ps aux | grep mem0` or check for processes listening on typical mem0 ports (default may be 8080 or 8000). Use `netstat -tlnp` or `ss -tlnp` to identify listening services.Affected if Mem0 server is actively listening on a network port and accessible to the target system.
-
Identify the mem0 versionCheck the installed mem0 package version. If using Python: `pip show mem0` or check requirements files for `mem0==1.0.0`. If running as a container: `docker ps` and inspect the image tag.Affected if The installed version is exactly 1.0.0.
-
Test unauthenticated access to POST /memoriesSend a crafted HTTP POST request without any Authorization header. Example using curl: `curl -X POST http://<server>:<port>/memories -H "Content-Type: application/json" -d '{"message":"test"}'` Check the HTTP response status code.Affected if The request succeeds with 2xx status (200/201) and creates a memory record without requiring any authentication credentials.
-
Inspect authentication configurationExamine the mem0 server configuration files or environment variables for authentication settings. Look for API_KEY, JWT_SECRET, OAUTH, or similar auth-related configuration. Check if authentication middleware is enabled in the server setup.Affected if No authentication mechanism (API keys, JWT, OAuth) is configured or enabled on the server.
If mem0 version 1.0.0 is running and the /memories endpoint accepts POST requests without any authentication credentials, the environment is vulnerable to CVE-2026-31245.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement authentication (e.g., API keys, JWT tokens, or OAuth 2.0) and role-based authorization checks on the POST /memories endpoint to verify user identity and permissions before allowing memory creation.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-31245 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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