CVE Catalog

CVE-2026-62264

HighCVSS 7.5
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.45%

39th percentile - higher than 39% of all known CVEs

Summary

In PDF Reader MCP versions 2.2.0 through 3.0.0, when the opt-in HTTP transport is enabled, the X-API-Key header is never validated despite startup logs claiming authentication is enabled. As a result, the /mcp endpoint accepts unauthenticated clients, and with the default 0.0.0.0 bind address anyone who can reach the port can invoke PDF tools and read any PDF the server process can open. URL-based sources also allow limited server-side request forgery, with private and loopback destinations blocked by default.

Risk Assessment

Unauthenticated access can lead to disclosure of PDF documents readable by the server process and limited internal network probing via SSRF. The risk applies only to deployments with the HTTP transport enabled.

Recommendation

Upgrade @sylphx/pdf-reader-mcp to version 3.0.1 or later. If HTTP transport is not needed, keep the default stdio transport and restrict network access to the port where applicable.

Related vulnerabilities

Original NVD description (English source)

PDF Reader MCP is a Model Context Protocol server for reading PDF documents. In versions 2.2.0 and later prior to 3.0.1, when `MCP_TRANSPORT=http` enables the opt-in HTTP server, `@sylphx/pdf-reader-mcp` reads `MCP_API_KEY` and logs that `X-API-Key` authentication is enabled but never validates the `X-API-Key` header on incoming requests. The `/mcp` endpoint consequently accepts unauthenticated clients. With the default bind address of `0.0.0.0`, any client able to reach the port can invoke every PDF tool and read any PDF the server process can open on the host, despite the misleading authentication-enabled startup log. URL-based sources additionally permit limited server-side request forgery; private and loopback destinations are blocked by default unless `--allow-private-ips` is set. The default `stdio` transport is unaffected. This issue is fixed in version 3.0.1.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS