<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 14 Oct 2026 21:56:50 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-323652</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-323652</link>
      <description>EUVD-2026-323652</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-323652</guid>
    </item>
    <item>
      <title>fkie_cve-2026-45609</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-45609</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-45609</guid>
    </item>
    <item>
      <title>GHSA-qjp4-4jvr-xqg3 — Spring AI MCP Security: Unvalidated URL Fetching (SSRF)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qjp4-4jvr-xqg3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.springaicommunity:mcp-client-security&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This only affects installations with Dynamic Client Registration (DCR) enabled:&lt;/p&gt;
&lt;p&gt;```properties
spring.ai.mcp.client.authorization.dynamic-client-registration.enabled=true
```&lt;/p&gt;
&lt;p&gt;DCR does not validate URLs exposed by MCP Servers (protected resource metadata URL, authorization server URL) and Authorization Servers (all OAuth2 endpoints).&lt;/p&gt;
&lt;p&gt;### Workaround&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Alternatively, users can provide the default implementations of these classes with a `RestClient` that implements URL filtering through `ClientHttpRequestInterceptor`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.springaicommunity:mcp-client-security&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This only affects installations with Dynamic Client Registration (DCR) enabled:&lt;/p&gt;
&lt;p&gt;```properties
spring.ai.mcp.client.authorization.dynamic-client-registration.enabled=true
```&lt;/p&gt;
&lt;p&gt;DCR does not validate URLs exposed by MCP Servers (protected resource metadata URL, authorization server URL) and Authorization Servers (all OAuth2 endpoints).&lt;/p&gt;
&lt;p&gt;### Workaround&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Alternatively, users can provide the default implementations of these classes with a `RestClient` that implements URL filtering through `ClientHttpRequestInterceptor`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qjp4-4jvr-xqg3</guid>
    </item>
  </channel>
</rss>
