Not ratedCVE-2026-111768

    SDK: Allocation of Resources Without Limits or Throttling (CVE-2026-111768)

    Published Sources: OSV, Hersteller

    What is affected, what to do

    Update Server to version 2.3.0, SDK to version 1.32.0.

    Affected
    • Server *..>= 2.0.0, < 2.3.0
    • SDK *..>= 1.3.0, < 1.32.0
    • SDK 1.3.0..*
    • Server 2.0.0..*
    Fixed in
    • Server 2.3.0
    • SDK 1.32.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    —

    Priority

    No value is available for this vulnerability.

    —

    CVSS v3

    No value is available for this vulnerability.

    —

    EPSS score

    No value is available for this vulnerability.

    Show all metrics
    Severity
    Not rated
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    30.00 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-770

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Summary

    In affected versions, servers put no limit on how many array elements and object keys they validated in one request. One HTTP request within the default 4 MiB size limit could exhaust the server's memory, and the process aborted with JavaScript heap out of memory.

    No credentials are needed, unless you authenticate requests before they reach the SDK.

    Am I affected?

    Yes, if clients you do not fully trust can reach your server over HTTP. The risk is highest for McpServer tools whose input contains an array or a record. stdio-only servers are not affected.

    Affected versions:

    • @modelcontextprotocol/sdk 1.3.0 through 1.31.0
    • @modelcontextprotocol/server 2.0.0 through 2.2.0

    Fix

    Upgrade to:

    • 1.x: @modelcontextprotocol/sdk 1.32.0 or later
    • 2.x: @modelcontextprotocol/server 2.3.0 or later

    Upgrading alone changes nothing. The patched versions add an McpServer option, maxToolInputElements, that is off by default. Make both of these changes:

    1. Set maxToolInputElements just above the largest input your tools need, for example new McpServer(info, { maxToolInputElements: 10_000 }). It counts array elements and object keys in a call's arguments. A call over the limit gets an isError: true result.
    2. Lower the request size limit to what your tools need. The option covers tool arguments only, and the size limit covers everything else. Set maxRequestBodySize on the transport or createMcpHandler(). If you parse the body yourself, for example with express.json() or Fastify, set that parser's limit.

    If you cannot upgrade yet, make the second change. maxRequestBodySize needs @modelcontextprotocol/sdk 1.30.1 or @modelcontextprotocol/server 2.1.0. Below that, use a reverse proxy.

    Source: OSV (Open Source Vulnerabilities), GitHub Security Advisories

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    VendorProductAffected versionsFixed in
    npm@modelcontextprotocol/sdk
    • >= 1.3.0, < 1.32.0
    • 1.3.0
    • 1.32.0
    • 1.32.0
    npm@modelcontextprotocol/server
    • 2.0.0
    • >= 2.0.0, < 2.3.0
    • 2.3.0
    • 2.3.0

    Weakness classes (CWE)

    • CWE-770Allocation of Resources Without Limits or Throttling

      Base

      The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

      Entry at MITRE CWE-770

    References & sources

    • github.commodelcontextprotocol/typescript-sdk/security/advisories/GHSA-46…web
    • github.commodelcontextprotocol/typescript-sdk/pull/2926web
    • github.commodelcontextprotocol/typescript-sdk/pull/2927web
    • github.commodelcontextprotocol/typescript-sdk/commit/6d8dbc6cb590edf766fc…web
    • github.commodelcontextprotocol/typescript-sdk/commit/fd26801b3b387742fe24…web
    • github.commodelcontextprotocol/typescript-sdkpackage
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-111768
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-111768"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-111768.svg?lang=en" alt="CVE-2026-111768 – NEOSEC Intel" height="20"></a>