Skip to content

NEWS, 5 NOV 2026, read 12 Nov 2026

MCP Inspector fixed for remote code execution through a hostile server's OAuth endpoint

All newsSee the full index

Pillar Security's write-up covers a remote code execution bug in the MCP Inspector, the debugging tool maintained by the Model Context Protocol project. A remote server answering with an OAuth challenge can name an authorization endpoint, and the client opened it with the open package. On Windows and WSL, open versions before 11.0.0 passed it to PowerShell unescaped.

Pillar says the code ran before the browser opened and without user approval, since auto-open was on by default in an interactive terminal. The maintainers shipped 2.12.0 and published GHSA-q978-78c7-phqw, rated High at CVSS 3.1 8.8. Pillar says the same chain affected opencode, fixed in 1.18.33, and open 11.0.0 contains the root-cause fix.

The notable point is scope. The Inspector exists to vet servers you do not trust, and the maintainers accepted that a hostile server is in scope. Any coding agent or IDE that implements the same OAuth flow should treat a remote MCP server as untrusted input.

What to check: Inspector, opencode and open versions on Windows and WSL developer machines, and your policy on connecting agents to remote MCP servers that nobody on the security team has reviewed.

Earlier and later in the release log

Every dated item is on the release log. Seen a release this log missed? Send a tip.

Sources

  1. pillar.security, read 12 Nov 2026

Last reviewed 12 Nov 2026.