SSRF (Server-Side Request Forgery) in org.springaicommunity:mcp-client-security (CVE-2026-45609)
Summary
SSRF in org.springaicommunity:mcp-client-security (CVE-2026-45609). Risk of unauthorized operations or information disclosure. Exploitable via McpOAuth2ClientManager. Mitigation: upgrade to 0.1.9 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45609 has been found in org.springaicommunity:mcp-client-security.
Attackers can target a specific entry point like McpOAuth2ClientManager over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.2/10.
What to do: upgrade org.springaicommunity:mcp-client-security to 0.1.9 or later.
If unsure, ask your IT team or search "org.springaicommunity:mcp-client-security CVE-2026-45609" on the vendor's site.
CVE-2026-45609 (org.springaicommunity:mcp-client-security) — CWE-918 / CVSS v3 7.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: McpOAuth2ClientManager / McpMetadataDiscoveryService / DynamicClientRegistrationService / RestClient
Patched: 0.1.9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in org.springaicommunity:mcp-client-security. Attackers reach the vulnerable code path via McpOAuth2ClientManager without authentication.
Check the vendor advisory for the affected versions of org.springaicommunity:mcp-client-security. Attack surface: McpOAuth2ClientManager / McpMetadataDiscoveryService / DynamicClientRegistrationService / RestClient.
Severity: High (CVSS 7.2/10). Risk of unauthorized operations or information disclosure.
Update to 0.1.9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.springaicommunity:mcp-client-security を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.springaicommunity:mcp-client-security to 0.1.9ステージング環境で 0.1.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com