Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-108859 – Denial of Service (unbounded POST body memory exhaustion) – mcp-go through 1.2.1

Be the first to know when new zero-days emerge:

Summary

CVE-2026-108859 is a denial-of-service vulnerability (CWE-770, Allocation of Resources Without Limits or Throttling) in mcp-go (github.com/mark3labs/mcp-go), a Go implementation of the Model Context Protocol. Remote, unauthenticated attackers can exhaust server memory by sending oversized POST bodies to the Streamable HTTP server. The CVE record rates it High: CVSS v4.0 8.7 (CVSS v3.1 7.5).

Technical details

  • Root cause: StreamableHTTPServer.ServeHTTP reads the entire POST request body with io.ReadAll before validating it, with no size limit.
  • Trigger conditions: The application exposes the mcp-go Streamable HTTP server over the network and accepts POST requests. No authentication or user interaction is required.
  • Attack vector: Network. The attacker sends very large POST bodies to the endpoint.
  • Impact: Memory exhaustion that degrades the service or crashes the server process (availability impact only). The CVE record lists no confidentiality or integrity impact.

Affected software

  • mcp-go (github.com/mark3labs/mcp-go) versions through 1.2.1 (all versions up to and including 1.2.1)

Severity

  • CVSS v4.0: 8.7 (High), CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
  • CVSS v3.1: 7.5 (High), CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Mitigation and recommended actions

  • Immediate: The CVE record does not name a fixed version. Check the mark3labs/mcp-go repository for a release newer than 1.2.1 that bounds request body size, and upgrade to it once confirmed.
  • If no patch is available: Place the Streamable HTTP endpoint behind a reverse proxy or API gateway that enforces a maximum request body size (for example, rejecting oversized POSTs). Restrict network access to trusted clients where possible, and apply container or process memory limits and restart policies to contain the impact.

References

Get a free Attack Surface scan to see if you’re exposed.

Get a free Attack Surface scan to see if you’re exposed.

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge