{"answers":{"affected":"2 open source packages ship an affected version, including org.springaicommunity:mcp-client-security. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-45609 in the wild and no public exploit code.","fix":"Upgrade org.springaicommunity:mcp-client-security to 0.1.9 or later.","what":"CVE-2026-45609 is a high-severity server-side request forgery vulnerability in spring-ai-community mcp-security, published on 29 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-45609 and fix it if it is affected.\n\nWhat it is: CVE-2026-45609 is a high-severity server-side request forgery vulnerability in spring-ai-community mcp-security, published on 29 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-45609 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.springaicommunity:mcp-client-security (Maven): affected all versions; fixed in 0.1.9\n- org.springaicommunity:mcp-client-security (Maven): affected all versions; fixed in 0.1.9\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-45609/ (Markdown: https://insights.sbomify.com/CVE-2026-45609/index.md)","id":"CVE-2026-45609","markdown":"https://insights.sbomify.com/CVE-2026-45609/index.md","name":"CVE-2026-45609","record":{"aliases":["GHSA-qjp4-4jvr-xqg3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Spring AI security library","requires_auth":"none","summary":"Attackers can exploit unvalidated URL fetching in mcp-security to access internal network resources when Dynamic Client Registration is enabled.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mcp_security","vendor":"springaicommunity"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"mcp-security provides Security and Authorization support for Model Context Protocol in Spring AI. Prior to 0.1.9, the mcp-security framework fails to implement the mandatory SSRF mitigations outlined in the Model Context Protocol (MCP) security specifications. Specifically, it processes untrusted URLs for OAuth-related discovery and metadata without verifying if the targets are malicious or internal to the network. This only affects installations with Dynamic Client Registration (DCR) enabled This vulnerability is fixed in 0.1.9.","ecosystems":["Maven"],"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-security: Unvalidated URL Fetching (SSRF)","id":"CVE-2026-45609","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"AVideo: 2FA toggle endpoint has no CSRF protection, letting an attacker page silently disable a logged-in victim's 2FA","id":"CVE-2026-45610"},"packages":[{"ecosystem":"Maven","fixed":["0.1.9"],"introduced":["0"],"last_affected":[],"package":"org.springaicommunity:mcp-client-security","purl":null,"source":"GHSA-qjp4-4jvr-xqg3"},{"ecosystem":"Maven","fixed":["0.1.9"],"introduced":["0"],"last_affected":[],"package":"org.springaicommunity:mcp-client-security","purl":"pkg:maven/org.springaicommunity/mcp-client-security","source":"GHSA-qjp4-4jvr-xqg3"}],"prev":{"headline":"Windows DHCP Client Information Disclosure Vulnerability","id":"CVE-2026-45608"},"products":["mcp-security"],"published":"2026-05-29","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":"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-02","vendors":["spring-ai-community"]},"summary":"Attackers can exploit unvalidated URL fetching in mcp-security to access internal network resources when Dynamic Client Registration is enabled.","url":"https://insights.sbomify.com/CVE-2026-45609/"}