{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-31244 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-31244 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-31244 is a medium-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-31244 and fix it if it is affected.\n\nWhat it is: CVE-2026-31244 is a medium-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-31244 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-31244/ (Markdown: https://insights.sbomify.com/CVE-2026-31244/index.md)","id":"CVE-2026-31244","markdown":"https://insights.sbomify.com/CVE-2026-31244/index.md","name":"CVE-2026-31244","record":{"aliases":["GHSA-4w6c-gfx3-vghv"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Memory server API","requires_auth":"none","summary":"Unauthenticated attackers can delete arbitrary memory records via the API, causing data loss and potential denial of service.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mem0","vendor":"mem0"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"The mem0 1.0.0 server lacks authentication and authorization controls for its memory deletion API endpoint (DELETE /memories/{memory_id}). The endpoint allows unauthenticated users to delete arbitrary memory records without verifying their identity or permissions. A remote attacker can exploit this by sending unauthenticated DELETE requests to remove any memory entry from the database, leading to unauthorized data loss and potential denial of service.","ecosystems":[],"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":"Missing authorization in n/a","id":"CVE-2026-31244","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"mem0 server lacks authentication and authorization controls for its memory creation API endpoint","id":"CVE-2026-31245"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2026-31243"},"products":["n/a"],"published":"2026-05-12","related":[{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2026-31242","kev_date_added":null,"published":"2026-05-12"},{"cvss_score":6.5,"headline":"mem0 server lacks authentication and authorization controls for its memory deletion API endpoint","id":"CVE-2026-31241","kev_date_added":null,"published":"2026-05-12"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2026-31243","kev_date_added":null,"published":"2026-05-12"},{"cvss_score":5.3,"headline":"mem0 server lacks authentication and authorization controls for its memory creation API endpoint","id":"CVE-2026-31245","kev_date_added":null,"published":"2026-05-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-13","vendors":["n/a"]},"summary":"Unauthenticated attackers can delete arbitrary memory records via the API, causing data loss and potential denial of service.","url":"https://insights.sbomify.com/CVE-2026-31244/"}