Vulnerability in mem0ai (CVE-2026-31240)
Summary
Vulnerability in mem0ai (CVE-2026-31240). Data can be tampered with by attackers. Exploitable via PUT /memories/{memory_id}.
Original description
The description as published by the source.
The mem0 1.0.0 server lacks authentication and authorization controls for its memory management API endpoints. Critical functions such as updating memory records (PUT /memories/{memory_id}) are exposed without any verification of the requester's identity or permissions. A remote attacker can exploit this by sending unauthenticated requests to modify, overwrite, or delete arbitrary memory records, leading to unauthorized data manipulation and potential data loss.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-31240 has been found in mem0ai.
Attackers can target a specific entry point like PUT /memories/{memory_id} over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "mem0ai CVE-2026-31240" on the vendor's site.
CVE-2026-31240 (mem0ai) — CWE-306 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: PUT /memories/{memory_id}
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-306) exists in mem0ai. Attackers reach the vulnerable code path via PUT /memories/{memory_id} without authentication.
Check the vendor advisory for the affected versions of mem0ai. Attack surface: PUT /memories/{memory_id}.
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PUT /memories/{memory_id} requests with malformed payloads or SQL meta-characters. Run grep -r 'mem0ai' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mem0ai' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mem0aiを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'PUT /memories/{memory_id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PUT /memories/{memory_id}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against PUT /memories/{memory_id} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web notion.so
- web github.com