Vulnerability in MCP Java SDK (CVE-2026-35568)
Summary
Vulnerability in MCP Java SDK (CVE-2026-35568). Data can be tampered with by attackers. Mitigation: upgrade to 1.0.0 or later.
Original description
The description as published by the source.
MCP Java SDK is the official Java SDK for Model Context Protocol servers and clients. Prior to 1.0.0, the java-sdk contains a DNS rebinding vulnerability. This vulnerability allows an attacker to access a locally or network-private java-sdk MCP server via a victims browser that is either local, or network adjacent. This allows an attacker to make any tool call to the server as if they were a locally running MCP connected AI agent. This vulnerability is fixed in 1.0.0.
Source: NIST National Vulnerability Database 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-35568 has been found in MCP Java SDK.
Data can be tampered with by attackers. CVSS score: 5.7/10.
What to do: upgrade MCP Java SDK to 1.0.0 or later.
If unsure, ask your IT team or search "MCP Java SDK CVE-2026-35568" on the vendor's site.
CVE-2026-35568 (MCP Java SDK) — CWE-346 / CVSS v3 5.7
Attack vector: adjacent-network / unauthenticated
Patched: 1.0.0 — 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.
A vulnerability (CWE-346) exists in MCP Java SDK.
Check the vendor advisory for the affected versions of MCP Java SDK.
Severity: Medium (CVSS 5.7/10). Data can be tampered with by attackers.
Update to 1.0.0.
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・依存マニフェストで MCP Java SDK を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade MCP Java SDK to 1.0.0ステージング環境で 1.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- web github.com