← Back
CVE-2026-45609
high
CVSS 7.2
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**SSRF** (CWE-918) exists in org.springaicommunity:mcp-client-security. Attackers reach the vulnerable code path via ``McpOAuth2ClientManager`` without authentication.
📍 Affected scope
org.springaicommunity:mcp-client-security — . Attack surface: `McpOAuth2ClientManager` / `McpMetadataDiscoveryService` / `DynamicClientRegistrationService` / `RestClient`.
🔥 Severity
Severity: High (CVSS 7.2/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.1.9**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.springaicommunity:mcp-client-security' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.springaicommunity:mcp-client-security' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.springaicommunity:mcp-client-security` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.springaicommunity:mcp-client-security to 0.1.9ステージング環境で 0.1.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.springaicommunity:mcp-client-security
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.1.9"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-45609
- package https://github.com/spring-ai-community/mcp-security
- web https://github.com/spring-ai-community/mcp-security/security/advisories/GHSA-qjp4-4jvr-xqg3
- web https://github.com/spring-ai-community/mcp-security/pull/68
- web https://github.com/spring-ai-community/mcp-security/commit/e6b67d8a67cd7acbee6e4c0741c385d62e3ed576
- web https://github.com/spring-ai-community/mcp-security/releases/tag/v0.1.9
- web https://github.com/advisories/GHSA-qjp4-4jvr-xqg3