MCP Inspector tool-output regex can freeze the user interface
A malicious server can advertise a computationally expensive pattern in a tool output schema. Synchronous validation of a returned result then monopolizes the interface thread.
Security incidents involving Model Context Protocol servers and tooling: supply-chain campaigns, credential disclosure, path traversal, and SSRF. Each entry links to primary sources and the disclosed CVE where one exists.
Showing 11 - 20 of 53
A malicious server can advertise a computationally expensive pattern in a tool output schema. Synchronous validation of a returned result then monopolizes the interface thread.
A nested repository metadata file can direct Git to a different repository. The server can then read or change that repository despite a configured repository boundary.
The example server exposes an environment-reading tool over unauthenticated HTTP with permissive browser-origin handling. A malicious web page can invoke it and receive secrets held in the server process environment.
The address guard and HTTP client interpret internationalized hostnames differently. An attacker-controlled domain can exploit that disagreement to direct the fetch tool to a private destination despite the public-address check.
On a case-insensitive filesystem, changing the spelling of an outward-pointing symlink can bypass a path check for a new file. The operating system still follows the link, creating the file beyond the allowed directory.
The allowlist comparison removes terminal quote or whitespace characters, while the subsequent filesystem operation uses the original path. A similarly named sibling directory can therefore pass a check intended for the allowed directory.
Origin-validation gaps combine with proxy behavior to let a malicious website obtain the Inspector token through DNS rebinding. The exposed credential can then authorize access to proxy-held secrets.
An embedded remote app runs on the proxy origin and can defeat the intended separation between app content and privileged proxy functions. Obtaining the proxy token gives the app access to local execution capabilities.
The network proxy reads an upstream response into memory and serializes it again for the browser. An oversized or never-ending response can therefore exhaust backend memory.
The fetch proxy can preserve caller-supplied authentication headers across a redirect to a different origin. A server controlling that redirect can receive credentials intended for the original destination.