{"answers":{"affected":"3 open source packages ship an affected version, including mcp-memory-service.","exploited":"There is no known exploitation of CVE-2026-50027 in the wild and no public exploit code.","fix":"Upgrade mcp-memory-service to 10.67.1 or later.","what":"CVE-2026-50027 is a critical missing authorization vulnerability in doobidoo mcp-memory-service, published on 14 Aug 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-50027 and fix it if it is affected.\n\nWhat it is: CVE-2026-50027 is a critical missing authorization vulnerability in doobidoo mcp-memory-service, published on 14 Aug 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-50027 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.67.1\n- mcp-memory-service (PyPI): affected all versions; fixed in 10.67.1\n- mcp-memory-service (PyPI): affected all versions; fixed in 10.67.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-50027/ (Markdown: https://insights.sbomify.com/CVE-2026-50027/index.md)","id":"CVE-2026-50027","markdown":"https://insights.sbomify.com/CVE-2026-50027/index.md","name":"CVE-2026-50027","record":{"aliases":["GHSA-84hp-mqvj-3p8h","PYSEC-2026-2624"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"AI memory service","requires_auth":"none","summary":"Unauthenticated attackers can read, write, and delete memory documents in mcp-memory-service due to missing authentication on specific API endpoints.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"mcp-memory-service is a semantic memory layer for AI applications. Prior to 10.67.1, all HTTP routes under /api/documents/* in mcp-memory-service are served without any authentication dependency, even when the server is configured with an API key (MCP_API_KEY) or OAuth. An unauthenticated remote attacker can upload arbitrary content into the memory store (write), retrieve stored document content (read), and permanently delete memories belonging to authenticated users (delete) — all without supplying any credentials. The /api/memories counterpart correctly enforces authentication, making this an inconsistent and exploitable authentication boundary. This vulnerability is fixed in 10.67.1.","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: Missing Authentication on Document API Endpoints Allows Unauthenticated Memory Read/Write/Delete","id":"CVE-2026-50027","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":"js-toml has silent type confusion via falsy-primitive duplicate-key bypass","id":"CVE-2026-50029"},"packages":[{"ecosystem":"PyPI","fixed":["10.67.1"],"introduced":["0"],"last_affected":[],"package":"mcp-memory-service","purl":null,"source":"GHSA-84hp-mqvj-3p8h"},{"ecosystem":"PyPI","fixed":["10.67.1"],"introduced":["0"],"last_affected":[],"package":"mcp-memory-service","purl":"pkg:pypi/mcp-memory-service","source":"GHSA-84hp-mqvj-3p8h"},{"ecosystem":"PyPI","fixed":["10.67.1"],"introduced":["0"],"last_affected":[],"package":"mcp-memory-service","purl":"pkg:pypi/mcp-memory-service","source":"PYSEC-2026-2624"}],"prev":{"headline":"Frappe: Lack of permissions checks in 'relink' and 'set_email_password' endpoints","id":"CVE-2026-50026"},"products":["mcp-memory-service"],"published":"2026-08-14","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":"total"},"state":"PUBLISHED","updated":"2026-08-17","vendors":["doobidoo"]},"summary":"Unauthenticated attackers can read, write, and delete memory documents in mcp-memory-service due to missing authentication on specific API endpoints.","url":"https://insights.sbomify.com/CVE-2026-50027/"}