Playbooks · Coding tasks
Two MCP servers patched holes this week
Written November 8, 2026
MCP Inspector 2.14.0 fixes three vulnerabilities and the AWS serverless MCP server patches a path traversal. Update first, audit second.
MCP Inspector 2.14.0: three fixes
MCP Inspector 2.14.0, released November 4, 2026, fixes three vulnerabilities reported privately against v2. The Inspector is the tool for testing MCP servers, so a flaw in it is a flaw in the thing you use to judge everything else. The three fixes are:
- An MCP App can no longer escape its sandbox frame (the frame-escape advisory). The proxy enforces a frame policy built from the app's approved Content Security Policy grants. When the frame starts to leave the document the host loaded, the proxy closes the relay, removes the frame, and tells the host why.
- Server.json import is now reviewed before it is saved (the server.json import advisory). The import shows the exact command before it is saved, and rejects a package with an invalid or empty environment-variable name or unsafe tokens. URL elicitations now open only http and https URLs — any other scheme is refused, with a reason — and the HTML preview's Content Security Policy now precedes all document markup.
- Server-supplied schema patterns are checked in bounded time (the schema-pattern advisory). Tool output and app elicitation schemas use a linear-time matcher with per-pattern and per-schema limits. A pattern beyond those limits is reported as unverified instead of being evaluated, so a hostile schema cannot stall validation.
One of the three, the schema-pattern fix, also affects the deprecated v1 line, where it is fixed in 1.0.4. The same release raises the Node floor to the October 2026 Node security releases — ^22.23.4 || ^24.22.1 || >=26.12.1 — and npm prints EBADENGINE on older versions. Upgrade with npx @modelcontextprotocol/inspector@latest.
AWS serverless MCP server: path traversal, fixed in 0.2.1
AWS published bulletin 2026-164-AWS on November 2, 2026, for CVE-2026-116635 in the AWS Serverless MCP Server. Improper limitation of a pathname in the deployment status component might allow an actor who can influence the MCP agent to read the contents of JSON files outside the intended deployment status directory — and, where write access has been enabled, to create or overwrite JSON files outside that directory. The issue is reachable through directory traversal sequences or an absolute path supplied in the project name input.
The affected range is versions before 0.2.1 of awslabs.aws-serverless-mcp-server, and the fix is 0.2.1. There are no workarounds; the bulletin recommends upgrading and ensuring any forked or derivative code is patched to incorporate the fix. The advisory is linked below.
The check
- Find which version of each you run. Check the Inspector version you launch —
npx @modelcontextprotocol/inspector@latestis the upgrade path, not the version check — and check the installed version ofawslabs.aws-serverless-mcp-serverin your MCP configuration. If you do not know which version you run, assume the older one. - Update both. Inspector to 2.14.0, or 1.0.4 if you are still on the deprecated v1 line; the AWS server to 0.2.1 or later. Check your Node version at the same time: the Inspector's new floor means an old Node prints
EBADENGINEinstead of running. - Audit which MCP servers you run at all. Patching the Inspector does not patch the servers it tests, and patching one AWS server does not patch the others in your configuration. List every MCP server in your setup, note which ones you actually use, and remove the ones you do not.
What these patches do not do
- The Inspector fixes do not fix the servers it tests. The Inspector is a testing tool. A server with its own flaw stays flawed after the Inspector is updated — the Inspector can now show you the flaw more safely, but the server still needs its own patch.
- The AWS fix does not cover forks automatically. Forked or derivative code needs the fix applied to it. Upgrading the package updates your install, not a copy someone vendored into another project.
- Neither advisory claims exploitation in the wild. The Inspector fixes were reported privately; the AWS bulletin describes the flaw and the fix without an exploitation report. Patch on the strength of the flaw, not on a breach report.
Limits
- This page reads the Inspector's release notes and the AWS security bulletin. It reports no exploit reproduction and no patch test here — the advisories were read, not independently tested against a running server.
- The flaw descriptions are the projects' own. Severity figures are not given in the release notes or the bulletin, and this page does not assign any.
- The Inspector's 1.0.4 fix covers the schema-pattern flaw only. The other two November fixes have no v1 release; the v1 line is deprecated, and staying on it means staying exposed to them.
Related playbooks
- Patch your MCP reference servers now
- MCP Inspector 2.15.0 fixes four vulnerabilities
- What broke in agent tools this week
- MCPhantom: agents install dead MCP servers
Sources
- MCP Inspector releases — Model Context Protocol
- CVE-2026-116635 — AWS Security Bulletin 2026-164-AWS
- AWS Serverless MCP Server path traversal advisory — awslabs/mcp
Back to: Coding playbooks hub · Also: MCPhantom: agents install dead MCP servers · 140 silent MCP contract changes, and how to pin them · A critical flaw in gemini-mcp-tool, fixed in 1.1.6