Vulnerabilities in pkg:maven/org.springaicommunity/mcp-client-security

PACKAGE
Advisory Identifier: GHSA-qjp4-4jvr-xqg3
Share
Advisory Summary

CVE-2026-45609 is a HIGH (CVSS 7.2) unvalidated url fetching (ssrf) vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Spring AI MCP Security libraries in the Maven ecosystem. The issue involves unvalidated url fetching (ssrf). Remediation is available by upgrading affected packages to version 0.1.9.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:maven/org.springaicommunity/mcp-client-security

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:maven/org.springaicommunity/mcp-client-security. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-qjp4-4jvr-xqg3 CVE-2026-45609 HIGH Spring AI MCP Security: Unvalidated URL Fetching (SSRF)

CVE-2026-45609 at a Glance

CVE Identifier CVE-2026-45609
GHSA Identifier GHSA-qjp4-4jvr-xqg3
Severity HIGH
CVSS v3.1 Base Score 7.2
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product Spring AI MCP Security
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-45609

To remediate this vulnerability, upgrade all affected Spring AI MCP Security dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.springaicommunity:mcp-client-security fixed: 0.1.9 
<dependency>
    <groupId>org.springaicommunity</groupId>
    <artifactId>mcp-client-security</artifactId>
    <version>0.1.9</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree -Dincludes=org.springaicommunity

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-45609, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.springaicommunity

Analyze the terminal output to locate any version of Spring AI MCP Security in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.1.9), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.springaicommunity command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Spring AI MCP Security, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The mcp-security framework fails to implement the mandatory SSRF mitigations outlined in the Model Context Protocol (MCP) [security specifications](https://modelcontextprotocol.io/docs/tutorials/security/security_best_practices#mitigation-3). 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`.

CVE-2026-45609 Affected Spring AI MCP Security Versions

1 component(s)
Fixed Versions:
0.1.9
Product / Package Ecosystem Affected Versions Fixed Version
org.springaicommunity:mcp-client-security
maven/org.springaicommunity/mcp-client-security
Maven
< 0.1.9
0.1.9

References

GitHub Advisory / Wiki ADVISORY
https://github.com/spring-ai-community/mcp-security/security/advisories/GHSA-qjp4-4jvr-xqg3
NVD — CVE-2026-45609 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-45609
Spring AI MCP Security Source Repository REPOSITORY
https://github.com/spring-ai-community/mcp-security/pull/68
Security Fix Commit FIX COMMIT
https://github.com/spring-ai-community/mcp-security/commit/e6b67d8a67cd7acbee6e4c0741c385d62e3ed576
Spring AI MCP Security Source Repository REPOSITORY
https://github.com/spring-ai-community/mcp-security
Spring AI MCP Security Release RELEASE
https://github.com/spring-ai-community/mcp-security/releases/tag/v0.1.9

Frequently Asked Questions

What is CVE-2026-45609?
CVE-2026-45609 is a security vulnerability in Spring AI MCP Security involving Unvalidated URL Fetching (SSRF) under CWE-918: Server-Side Request Forgery (SSRF).
Which Spring AI MCP Security versions are affected?
Affected versions include releases prior to 0.1.9 across affected packages: org.springaicommunity:mcp-client-security.
What version fixes CVE-2026-45609?
Upgrading to 0.1.9 (or the latest patched release for your respective branch) resolves the vulnerability.
Is mcp-client-security affected?
Yes, org.springaicommunity:mcp-client-security is affected in releases prior to 0.1.9. Upgrade your dependency to 0.1.9 or later.
What is the CVSS score of CVE-2026-45609?
CVE-2026-45609 has a CVSS v3.1 base score of 7.2 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N.
What CWE is associated with CVE-2026-45609?
CVE-2026-45609 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check Maven dependencies for CVE-2026-45609?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.springaicommunity'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qjp4-4jvr-xqg3",
  "modified" : "2026-06-09T10:29:26Z",
  "published" : "2026-05-18T13:29:29Z",
  "aliases" : [ "CVE-2026-45609" ],
  "summary" : "Spring AI MCP Security: Unvalidated URL Fetching (SSRF)",
  "details" : "### Summary\n\nThe mcp-security framework fails to implement the mandatory SSRF mitigations outlined in the Model Context Protocol (MCP) [security specifications](https://modelcontextprotocol.io/docs/tutorials/security/security_best_practices#mitigation-3). Specifically, it processes untrusted URLs for OAuth-related discovery and metadata without verifying if the targets are malicious or internal to the network.\n\nThis only affects installations with Dynamic Client Registration (DCR) enabled:\n\n```properties\nspring.ai.mcp.client.authorization.dynamic-client-registration.enabled=true\n```\n\nDCR does not validate URLs exposed by MCP Servers (protected resource metadata URL, authorization server URL) and Authorization Servers (all OAuth2 endpoints).\n\n### Workaround\n\nWhen 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.\n\nAlternatively, users can provide the default implementations of these classes with a `RestClient` that implements URL filtering through `ClientHttpRequestInterceptor`.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.springaicommunity:mcp-client-security"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.1.9"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/spring-ai-community/mcp-security/security/advisories/GHSA-qjp4-4jvr-xqg3"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-45609"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/spring-ai-community/mcp-security/pull/68"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/spring-ai-community/mcp-security/commit/e6b67d8a67cd7acbee6e4c0741c385d62e3ed576"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/spring-ai-community/mcp-security"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/spring-ai-community/mcp-security/releases/tag/v0.1.9"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-18T13:29:29Z",
    "nvd_published_at" : "2026-05-29T15:16:23Z"
  }
}