{"answers":{"affected":"3 open source packages ship an affected version, including mcp-memory-service.","exploited":"There is no known exploitation of CVE-2026-49291 in the wild and no public exploit code.","fix":"Upgrade mcp-memory-service to 10.65.3 or later.","what":"CVE-2026-49291 is a high-severity missing authorization vulnerability in doobidoo mcp-memory-service, published on 19 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-49291 and fix it if it is affected.\n\nWhat it is: CVE-2026-49291 is a high-severity missing authorization vulnerability in doobidoo mcp-memory-service, published on 19 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-49291 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mcp-memory-service (PyPI): affected all versions; fixed in 10.65.3\n- mcp-memory-service (PyPI): affected all versions; fixed in 10.65.3\n- mcp-memory-service (PyPI): affected all versions; fixed in 10.65.3\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-49291/ (Markdown: https://insights.sbomify.com/CVE-2026-49291/index.md)","id":"CVE-2026-49291","markdown":"https://insights.sbomify.com/CVE-2026-49291/index.md","name":"CVE-2026-49291","record":{"aliases":["GHSA-2r68-g678-7qr3","PYSEC-2026-2622"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"AI memory service","requires_auth":"low_privilege","summary":"Read-only OAuth clients can modify or delete memories via MCP tools due to missing authorization checks on the JSON-RPC endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"mcp-memory-service is a semantic memory layer for AI applications. Prior to version 10.65.3, the HTTP MCP JSON-RPC endpoint at `/mcp` requires only OAuth `read` scope for all requests, then dispatches `tools/call` directly to handlers that include mutating tools. A read-only OAuth client can call `store_memory` and `delete_memory` through MCP even though the corresponding REST endpoints require `write` scope. Version 10.65.3 patches the issue.","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":true,"headline":"mcp-memory-service: OAuth read-only clients can write and delete memories through MCP tools/call","id":"CVE-2026-49291","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Kiwi TCMS: The /init-db/ page renders and responds to requests after first use","id":"CVE-2026-49292"},"packages":[{"ecosystem":"PyPI","fixed":["10.65.3"],"introduced":["0"],"last_affected":[],"package":"mcp-memory-service","purl":null,"source":"GHSA-2r68-g678-7qr3"},{"ecosystem":"PyPI","fixed":["10.65.3"],"introduced":["0"],"last_affected":[],"package":"mcp-memory-service","purl":"pkg:pypi/mcp-memory-service","source":"GHSA-2r68-g678-7qr3"},{"ecosystem":"PyPI","fixed":["10.65.3"],"introduced":["0"],"last_affected":[],"package":"mcp-memory-service","purl":"pkg:pypi/mcp-memory-service","source":"PYSEC-2026-2622"}],"prev":{"headline":"Slopsmith has path traversal in archive extractors that allows arbitrary file write → potential RCE","id":"CVE-2026-49290"},"products":["mcp-memory-service"],"published":"2026-06-19","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-22","vendors":["doobidoo"]},"summary":"Read-only OAuth clients can modify or delete memories via MCP tools due to missing authorization checks on the JSON-RPC endpoint.","url":"https://insights.sbomify.com/CVE-2026-49291/"}