CVE-2026-31243
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 reset and table re-creation functionality accessible via the DELETE /memories endpoint. An unauthenticated attacker can send a DELETE request that triggers a reset operation, leading to the execution of a CREATE TABLE SQL statement. This can cause unexpected table re-creation, schema disruption, potential data loss, and denial of service for the memory management service.
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 has a critical authentication/authorization bypass vulnerability where the DELETE /memories endpoint lacks access controls. An unauthenticated attacker can send DELETE requests that trigger memory reset operations and execute CREATE TABLE SQL statements, causing schema disruption, potential data loss, and denial of service.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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.
-
Identify installed mem0 versionCheck the installed package version using pip show mem0 or check the requirements file for 'mem0==1.0.0' or inspect the installed package metadataAffected if The installed version is exactly 1.0.0 (mem0==1.0.0)
-
Verify if the server is runningCheck running processes or container status for the mem0 server (look for 'mem0' or 'mem0 server' process, or check if port 8000/8080 is listening)Affected if The mem0 1.0.0 server process is running and exposed on a network port
-
Confirm DELETE endpoint is accessibleSend a DELETE request to /memories endpoint without any Authorization header: curl -X DELETE http://<server>:<port>/memoriesAffected if The DELETE /memories endpoint responds with anything other than 401 Unauthorized or 403 Forbidden (e.g., 200, 204, or 500) without requiring authentication
-
Check server authentication configurationInspect the mem0 server configuration files or environment variables for AUTH_ENABLED, AUTHENTICATION_ENABLED, or similar flags, or examine the server startup command for auth-related flagsAffected if Authentication is disabled, not configured, or the configuration file explicitly lacks authentication for the DELETE /memories endpoint
-
Test for SQL statement execution capabilitySend a DELETE request with a payload containing SQL-like content (e.g., CREATE TABLE test...) to /memories and observe if any SQL statements are processed or if schema changes occurAffected if The endpoint accepts and processes arbitrary content that can trigger SQL statement execution, leading to schema disruption
A user is affected if they are running mem0 version 1.0.0 with the DELETE /memories endpoint exposed and authentication not enforced on that endpoint.
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 and role-based authorization for the DELETE /memories endpoint and all memory management endpoints. Add input validation to prevent arbitrary SQL statement execution.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31243 — 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-31243 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