Skip to content
VulniPulse
High7.5Red Hat Linux

CVE-2026-111768: Red Hat @modelcontextprotocol/sdk: @modelcontextprotocol/server: Model Context Protocol TypeScript SDK: Denial of service via memory exhaustion from crafted HTTP requests

This Red Hat advisory covers CVE-2026-111768.

Open the Red Hat advisory

Key facts

Vendor rating
High, CVSS 7.5
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H · base score 7.5, scored by GitHub_MAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: none. Availability impact: high.
Weakness
  • CWE-770: Allocation of Resources Without Limits or Throttling
EPSS
0.60% chance of exploitation in the next 30 days (49th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
CISA KEV
Not listed (catalogue checked )
Fixed in
1.32.0
Source published
Listed by VulniPulse

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Related products & platforms

Red Hat LinuxUnclassified

Description

@modelcontextprotocol/sdk: @modelcontextprotocol/server: Model Context Protocol TypeScript SDK: Denial of service via memory exhaustion from crafted HTTP requests. Red Hat rates this important (CVSS 7.5).

Weakness: CWE-770.

Text from the source record.

How to fix CVE-2026-111768

Upgrade to a fixed release named by Red Hat:

  • 1.32.0

Vendor guidance

  • To mitigate this vulnerability without applying code changes, implement one or more of the following operational controls: 1. Restrict transport exposure: Run Model Context Protocol services using the stdio transport instead of HTTP where feasible. If HTTP endpoints are required, restrict network access to trusted hosts using network firewall rules or access control lists. 2. Enforce request body size limits at the reverse proxy or API gateway: Place the application behind a reverse proxy (such as NGINX or Apache HTTP Server) or ingress controller and reduce the maximum permitted request body size to the minimum required for expected traffic. For example, in an upstream NGINX configuration: ``` client_max_body_size 256k; ``` Warning: Modifying reverse proxy or firewall configurations may require reloading or restarting the service (for example, `systemctl reload nginx`), which can cause temporary interruptions to active network sessions. Ensure the chosen payload limit is tested to avoid dropping valid application requests.

All Red Hat Linux advisories

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Red Hat