Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-34237 medium CVSS 6.1

Vulnerability in io.modelcontextprotocol.sdk:mcp-core (CVE-2026-34237)

Summary

Vulnerability in io.modelcontextprotocol.sdk:mcp-core (CVE-2026-34237). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.18.3 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 versions 0.83.0, 1.0.1, and 1.1.1, there is a hardcoded wildcard CORS vulnerability. This issue has been patched in versions 0.83.0, 1.0.1, and 1.1.1.

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-34237 has been found in io.modelcontextprotocol.sdk:mcp-core.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade io.modelcontextprotocol.sdk:mcp-core to 0.18.3 or later.
If unsure, ask your IT team or search "io.modelcontextprotocol.sdk:mcp-core CVE-2026-34237" on the vendor's site.

CVE-2026-34237 (io.modelcontextprotocol.sdk:mcp-core) — CWE-942 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.18.3 — 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

A vulnerability (CWE-942) exists in io.modelcontextprotocol.sdk:mcp-core.

📍 Affected scope

Check the vendor advisory for the affected versions of io.modelcontextprotocol.sdk:mcp-core.

🔥 Severity

Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.18.3.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで io.modelcontextprotocol.sdk:mcp-core を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade io.modelcontextprotocol.sdk:mcp-core to 0.18.3

    ステージング環境で 0.18.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven io.modelcontextprotocol.sdk:mcp-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.18.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details