My MCP Security Scanner Missed 2026's Worst MCP RCE: Here Is the One-Rule Fix

The hook

A few months back I shipped mcpscan, a static analyzer that scans MCP (Model Context Protocol) servers for the vulnerability classes that keep showing up in this ecosystem: command injection, SSRF, and path traversal. Rule MCP007 was supposed to be the path traversal catch-all.

This week I sat down with my own research notes and ran a simple gut-check: would MCP007 have caught the four real path-traversal CVEs disclosed against MCP servers this year?

It would have missed every single one. Including the worst one.

Real-world context

My MCP Security Scanner Missed 2026's Worst MCP RCE: Here Is the One-Rule Fix

Related reading

The MCP Vulnerability That Lives Between Servers, Not In One

MCP security scanners are wrong about four findings in five, and the cause is…

I found a confirmed bug in the official MCP SDK while building a red-team tool…

Show HN: We scanned 23 public MCP servers for CVEs - Here is what broke

Your MCP Server Is Probably Overprivileged - Here's a Scanner For It

I scanned 670 MCP servers and 78% have significant security issues