{"answers":{"affected":"3 open source packages ship an affected version, including mem0ai.","exploited":"There is no known exploitation of CVE-2026-31240 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-31240 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-31240 is a high-severity missing authorization vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-31240 and fix it if it is affected.\n\nWhat it is: CVE-2026-31240 is a high-severity missing authorization vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-31240 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mem0ai (PyPI): affected all versions up to 1.0.0; no fix listed\n- mem0ai (PyPI): affected all versions up to 1.0.0; no fix listed\n- mem0ai (PyPI): affected all versions up to 1.0.0; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-31240/ (Markdown: https://insights.sbomify.com/CVE-2026-31240/index.md)","id":"CVE-2026-31240","markdown":"https://insights.sbomify.com/CVE-2026-31240/index.md","name":"CVE-2026-31240","record":{"aliases":["GHSA-jfv9-68m5-gjjr","PYSEC-2026-2635"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python memory library","requires_auth":"none","summary":"Remote attackers can modify or delete memory records in the mem0 server due to missing authentication and authorization controls on API endpoints.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"mem0 server lacks authentication and authorization controls for its memory management API endpoints","id":"CVE-2026-31240","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"mem0 server lacks authentication and authorization controls for its memory deletion API endpoint","id":"CVE-2026-31241"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"mem0ai","purl":null,"source":"GHSA-jfv9-68m5-gjjr"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"mem0ai","purl":"pkg:pypi/mem0ai","source":"GHSA-jfv9-68m5-gjjr"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"mem0ai","purl":"pkg:pypi/mem0ai","source":"PYSEC-2026-2635"}],"prev":{"headline":"mamba language model framework vulnerable to insecure deserialization when loading pre-trained models from HuggingFace Hub","id":"CVE-2026-31239"},"products":["n/a"],"published":"2026-05-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-14","vendors":["n/a"]},"summary":"Remote attackers can modify or delete memory records in the mem0 server due to missing authentication and authorization controls on API endpoints.","url":"https://insights.sbomify.com/CVE-2026-31240/"}