mediumresolved

MCP Inspector fetch proxy response has no effective memory bound

The network proxy reads an upstream response into memory and serializes it again for the browser. An oversized or never-ending response can therefore exhaust backend memory.

The network proxy reads an upstream response into memory and serializes it again for the browser. An oversized or never-ending response can therefore exhaust backend memory.

This is a maintainer-documented vulnerability disclosure. The advisory lists affected ranges: @modelcontextprotocol/inspector >= 2.0.0, <= 2.11.0; @modelcontextprotocol/inspector >= 0.21.2, <= 1.0.2; @modelcontextprotocol/inspector-server >= 0.21.2, <= 1.0.2. Patched release lines: @modelcontextprotocol/inspector 1.0.3; @modelcontextprotocol/inspector 2.12.0; @modelcontextprotocol/inspector-server 1.0.3. Consult the specific advisory for configuration requirements and branch coverage.

Takeaway

Use a patched release on a supported branch and verify the relevant browser, process or session boundary. Keep untrusted MCP endpoints and imported configurations outside privileged runtime contexts.

Sources

mcpinspectorghsa-m5pj-3536-3xcp