GitHub Advisoryadvisory · Maven

GHSA-qjp4-4jvr-xqg3 Spring AI MCP Security: Unvalidated URL Fetching (SSRF)

HIGH Published 2026-05-18 Modified 2026-06-09 Official page ↗
Aliases
CVE-2026-45609
Ecosystem
Maven
Packages
org.springaicommunity:mcp-client-security
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Weaknesses
CWE-918
Reviewed
2026-05-18

Affected packages

• Maven org.springaicommunity:mcp-client-security: < 0.1.9 → fixed in 0.1.9

Description

Summary 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: ```properties spring.ai.mcp.client.authorization.dynamic-client-registration.enabled=true ``` DCR does not validate URLs exposed by MCP Servers (protected resource metadata URL, authorization server URL) and Authorization Servers (all OAuth2 endpoints). Workaround When users need to perform DCR, they may provide their own `McpOAuth2ClientManager`. Both `McpMetadataDiscoveryService` and `DynamicClientRegistrationService` are also affected, if used, users should provide their own subclasses. Alternatively, users can provide the default implementations of these classes with a `RestClient` that implements URL filtering through `ClientHttpRequestInterceptor`.

Related

Alias · CVE (1)

  • CVE-2026-45609 mcp-security provides Security and Authorization support for Model Context Protocol in Spring AI. vulnerability

Weakness · CWE (1)

  • CWE-918 Server-Side Request Forgery weakness

References