Skip to content

[GHSA-m5pj-3536-3xcp] - [v1] - /fetch proxy has no size cap on the proxied response body (memory-exhaustion DoS) #2781

Closed

Description

@cliffhall

Advisory: GHSA-m5pj-3536-3xcp

Affected versions: @modelcontextprotocol/inspector and @modelcontextprotocol/inspector-server >= 0.21.2, <= 1.0.2 (v1 half; the v2 half, >= 2.0.0, <= 2.11.0, is #2780)

Reporter: @CloneOfAlex

Severity: medium | Reported: 2026-09-18


The v1 proxy's /fetch route read the upstream response body with no size cap, so a remote server could exhaust the proxy's memory with an oversized response. The advisory holds the full report.

This issue tracks the v1 line. The advisory's draft card was converted into the v2 issue, #2780, so this one was filed separately for board #11.

Activity

  1. cliffhall commented on Oct 22, 2026

    @cliffhall
    MemberAuthor

    Shipped in 1.0.3, published to npm under v1-latest. Advisory: GHSA-m5pj-3536-3xcp.

    Landed on v1/main in merge commit e9cd45b9, together with GHSA-wmjf-2m46-2352 (#2756). The fix commits:

    • 7e6c03dc fix(server): cap the /fetch response body
    • 5542ab8c fix(server): decode the capped /fetch body like response.text()
    • ccb8a3ad test(server): drive the /fetch route's body cap end to end

    The v2 half is #2780 and shipped in 2.12.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingv1

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions