highresolved

MCP Inspector missing-Origin handling bypasses process-launch authentication

The maintainer documents an incomplete earlier fix in which requests without an Origin header regain access to a sensitive process-launch function. The authentication boundary must hold even when that optional browser header is absent.

The maintainer documents an incomplete earlier fix in which requests without an Origin header regain access to a sensitive process-launch function. The authentication boundary must hold even when that optional browser header is absent.

This is a maintainer-documented vulnerability disclosure. The advisory lists affected ranges: @modelcontextprotocol/inspector >= 0.14.1, <= 1.0.2; @modelcontextprotocol/inspector-server >= 0.14.1, <= 1.0.2. Patched release lines: @modelcontextprotocol/inspector 1.0.3; @modelcontextprotocol/inspector-server 1.0.3. Consult the specific advisory for configuration requirements and branch coverage.

Takeaway

Use a patched release on a supported branch and verify the relevant browser, process or session boundary. Keep untrusted MCP endpoints and imported configurations outside privileged runtime contexts.

Sources

mcpinspectorghsa-wmjf-2m46-2352