Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

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:

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

  1. Find which version of each you run. Check the Inspector version you launch — npx @modelcontextprotocol/inspector@latest is the upgrade path, not the version check — and check the installed version of awslabs.aws-serverless-mcp-server in your MCP configuration. If you do not know which version you run, assume the older one.
  2. 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 EBADENGINE instead of running.
  3. 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

Limits

Related playbooks

Sources

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