{"answers":{"affected":"3 open source packages ship an affected version, including mcp-memory-service. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33010 exists.","fix":"Upgrade mcp-memory-service to 10.25.1 or later.","what":"CVE-2026-33010 is a high-severity vulnerability in doobidoo mcp-memory-service, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-33010 and fix it if it is affected.\n\nWhat it is: CVE-2026-33010 is a high-severity vulnerability in doobidoo mcp-memory-service, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33010 exists.\n\nAffected packages and fixed versions:\n- mcp-memory-service (PyPI): affected all versions; fixed in 10.25.1\n- mcp-memory-service (PyPI): affected all versions; fixed in 10.25.1\n- mcp-memory-service (PyPI): affected all versions; fixed in 10.25.1\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-33010/ (Markdown: https://insights.sbomify.com/CVE-2026-33010/index.md)","id":"CVE-2026-33010","markdown":"https://insights.sbomify.com/CVE-2026-33010/index.md","name":"CVE-2026-33010","record":{"aliases":["GHSA-g9rg-8vq5-mpwm","PYSEC-2026-2625"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"MCP memory backend","requires_auth":"none","summary":"Misconfigured CORS allows malicious websites to read, modify, and delete stored memories in mcp-memory-service when HTTP and anonymous access are enabled.","user_interaction":"required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mcp-memory-service","vendor":"doobidoo"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-942","name":"Permissive Cross-domain Security Policy with Untrusted Domains"}],"description":"mcp-memory-service is an open-source memory backend for multi-agent systems. Prior to version 10.25.1, when the HTTP server is enabled (MCP_HTTP_ENABLED=true), the application configures FastAPI's CORSMiddleware with allow_origins=['*'], allow_credentials=True, allow_methods=[\"*\"], and allow_headers=[\"*\"]. The wildcard Access-Control-Allow-Origin: * header permits any website to read API responses cross-origin. When combined with anonymous access (MCP_ALLOW_ANONYMOUS_ACCESS=true) - the simplest way to get the HTTP dashboard working without OAuth - no credentials are needed, so any malicious website can silently read, modify, and delete all stored memories. This issue has been patched in version 10.25.1.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"mcp-memory-service's Wildcard CORS with Credentials Enables Cross-Origin Memory Theft","id":"CVE-2026-33010","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"misconfiguration","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Nest Fastify HEAD Request Middleware Bypass","id":"CVE-2026-33011"},"packages":[{"ecosystem":"PyPI","fixed":["10.25.1"],"introduced":["0"],"last_affected":[],"package":"mcp-memory-service","purl":null,"source":"GHSA-g9rg-8vq5-mpwm"},{"ecosystem":"PyPI","fixed":["10.25.1"],"introduced":["0"],"last_affected":[],"package":"mcp-memory-service","purl":"pkg:pypi/mcp-memory-service","source":"GHSA-g9rg-8vq5-mpwm"},{"ecosystem":"PyPI","fixed":["10.25.1"],"introduced":["0"],"last_affected":[],"package":"mcp-memory-service","purl":"pkg:pypi/mcp-memory-service","source":"PYSEC-2026-2625"}],"prev":{"headline":"EVerest: MQTT Switch-Phases Command Data Race Causing Charger State Corruptio","id":"CVE-2026-33009"},"products":["mcp-memory-service"],"published":"2026-03-20","related":[{"cvss_score":5.3,"headline":"mcp-memory-service: System Information Disclosure via Health Endpoint","id":"CVE-2026-29787","kev_date_added":null,"published":"2026-03-07"}],"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":"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-20","vendors":["doobidoo"]},"summary":"Misconfigured CORS allows malicious websites to read, modify, and delete stored memories in mcp-memory-service when HTTP and anonymous access are enabled.","url":"https://insights.sbomify.com/CVE-2026-33010/"}