Playbooks · Coding tasks
MCP Inspector 2.15.0 fixes four vulnerabilities
Written November 16, 2026
MCP Inspector 2.15.0 fixes four vulnerabilities: cloud metadata addresses, an unbounded stream, env values in previews, and a daemon check.
The 2.15.0 release notes, dated November 12, 2026, lead with security. The release fixes four vulnerabilities in the MCP Inspector, the tool developers run to test MCP servers before connecting real clients to them. Three of the four affect long stretches of the v2 line, and one affects only the release just before this one. The notes give one upgrade command for everyone: npx @modelcontextprotocol/inspector@latest. If you run the Inspector against servers you do not control, or on a cloud machine, this is the release to move to before your next session.
Cloud metadata addresses are now blocked
The fetch guard now blocks cloud metadata addresses outside 169.254.0.0/16. The notes name 100.100.100.200 and 192.0.0.192, and say the block also covers their decimal and IPv4-mapped IPv6 forms, so writing the same address a different way does not get around it. Neither the /api/fetch proxy nor OAuth discovery can be pointed at those addresses any more. This fix, tracked as GHSA-fvg8-f358-w2c8, affects every v2 release from 2.0.0 through 2.14.0. Metadata addresses are a common target because a cloud instance can hand out credentials to anything that can reach them, so a testing tool that could be aimed at them was a real exposure, not a theoretical one.
An unbounded stream can no longer take down every session
The network tracker now caps the body it records for a POST event-stream response. Before this fix, a server streaming an unbounded response could exhaust the web backend's memory and take down every session running through it, as GHSA-9w48-x22j-rrm7 describes. One misbehaving or hostile server was enough; the person testing it lost the whole backend, not just that one connection. This fix also affects every v2 release from 2.0.0 through 2.14.0. For anyone who points the Inspector at third-party servers as part of reviewing them, the cap removes a simple way for a server under test to crash the tool doing the testing.
Launch previews show every env value
The server.json launch preview now shows every environment variable's value instead of hiding them. It flags runtime-control variables such as NODE_OPTIONS and npm_config_registry with a warning, and it requires confirmation before the server can be added. The advisory, GHSA-pp85-586h-2m95, affects 2.14.0 only. The change matters because a server configuration can carry variables that change how the runtime itself behaves, not just settings for the server. When those values were hidden in the preview, a person could approve a launch without seeing the parts most worth reading. Now the values are on screen, the risky ones are marked, and adding the server takes an explicit confirmation.
mcpdo asks the daemon to prove itself first
mcpdo now asks the connection daemon to show that it holds this user's token before sending it anything. An impostor listening on the daemon's socket or pipe receives no credentials, because it cannot produce the token. The advisory is GHSA-5572-x678-xmv8, and the affected range is 2.10.0 through 2.14.0. The other three fixes assume the server under test might be hostile; this one covers the local side, where another process on the same machine could sit on the socket and wait for credentials to arrive. The token exchange now runs in the safer direction: the daemon speaks first.
What to do
- Upgrade. Run
npx @modelcontextprotocol/inspector@latest, as the release notes state. Every v2 release from 2.0.0 through 2.14.0 carries at least two of these four issues. - Note your range. The fetch guard and event-stream fixes span 2.0.0–2.14.0, the daemon fix spans 2.10.0–2.14.0, and the preview fix is 2.14.0 only.
- Read previews fully. On 2.15.0 the launch preview shows all env values; warnings on variables such as
NODE_OPTIONSare worth a pause before confirming.
The release also carries ordinary changes, including a smaller Docker runtime image, per-tool run history in the web UI, and a --load-scenario option for load runs. Those are secondary. The reason to move now is the four fixes above, and a separate set of MCP server patches covered in the page linked below is a different story about different software.
Related playbooks
- Two MCP servers patched holes this week
- Patch your MCP reference servers now
- Coding-agent traces in advisory fixes
- Manage Airbyte pipelines through its MCP server
Sources
- MCP Inspector 2.15.0 release notes — GitHub — the four security fixes, their GHSA identifiers, the affected version ranges, and the upgrade command.
- GHSA-fvg8-f358-w2c8 — GitHub advisory — the fetch guard and cloud metadata addresses.
- GHSA-9w48-x22j-rrm7 — GitHub advisory — the event-stream body cap.
- GHSA-pp85-586h-2m95 — GitHub advisory — env values in the server.json launch preview.
- GHSA-5572-x678-xmv8 — GitHub advisory — the mcpdo daemon token exchange.
Back to: Coding playbooks hub · Also: Two MCP servers patched holes this week