{"answers":{"affected":"3 open source packages ship an affected version, including mcp-neo4j-cypher.","exploited":"There is no known exploitation of CVE-2026-35402 in the wild and no public exploit code.","fix":"Upgrade mcp-neo4j-cypher to 0.6.0 or later.","what":"CVE-2026-35402 is a low-severity server-side request forgery vulnerability in neo4j-contrib mcp-neo4j, published on 17 Apr 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-35402 and fix it if it is affected.\n\nWhat it is: CVE-2026-35402 is a low-severity server-side request forgery vulnerability in neo4j-contrib mcp-neo4j, published on 17 Apr 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-35402 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mcp-neo4j-cypher (PyPI): affected all versions; fixed in 0.6.0\n- mcp-neo4j-cypher (PyPI): affected all versions; fixed in 0.6.0\n- mcp-neo4j-cypher (PyPI): affected all versions; fixed in 0.6.0\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-35402/ (Markdown: https://insights.sbomify.com/CVE-2026-35402/index.md)","id":"CVE-2026-35402","markdown":"https://insights.sbomify.com/CVE-2026-35402/index.md","name":"CVE-2026-35402","record":{"aliases":["GHSA-x3cv-r3g3-fpg9","PYSEC-2026-2626"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Neo4j MCP server","requires_auth":"low_privilege","summary":"Attackers can bypass read-only restrictions in the Neo4j MCP server to perform unauthorized write operations or server-side request forgery.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"mcp-neo4j-cypher is an MCP server for executing Cypher queries against Neo4j databases. In versions prior to 0.6.0, the read_only mode enforcement can be bypassed using APOC CALL procedures, potentially allowing unauthorized write operations or server-side request forgery. This issue is fixed in version 0.6.0.","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-neo4j-cypher: SSRF and Data Modification via read_only Mode Bypass Through CALL Procedures","id":"CVE-2026-35402","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"LORIS has potential cross-site scripting in survey_accounts module","id":"CVE-2026-35403"},"packages":[{"ecosystem":"PyPI","fixed":["0.6.0"],"introduced":["0"],"last_affected":[],"package":"mcp-neo4j-cypher","purl":null,"source":"GHSA-x3cv-r3g3-fpg9"},{"ecosystem":"PyPI","fixed":["0.6.0"],"introduced":["0"],"last_affected":[],"package":"mcp-neo4j-cypher","purl":"pkg:pypi/mcp-neo4j-cypher","source":"GHSA-x3cv-r3g3-fpg9"},{"ecosystem":"PyPI","fixed":["0.6.0"],"introduced":["0"],"last_affected":[],"package":"mcp-neo4j-cypher","purl":"pkg:pypi/mcp-neo4j-cypher","source":"PYSEC-2026-2626"}],"prev":{"headline":"Saleor has a resource exhaustion vulnerability in GraphQL queries","id":"CVE-2026-35401"},"products":["mcp-neo4j"],"published":"2026-04-17","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":"partial"},"state":"PUBLISHED","updated":"2026-04-20","vendors":["neo4j-contrib"]},"summary":"Attackers can bypass read-only restrictions in the Neo4j MCP server to perform unauthorized write operations or server-side request forgery.","url":"https://insights.sbomify.com/CVE-2026-35402/"}