Answer in brief
CVE-2026-62264 records a High severity (CVSS 7.5) vulnerability in PDF Reader MCP: HTTP transport accepts unauthenticated requests despite a configured MCP_API_KEY. The current sources do not mark it as known exploited. The current feed maps SylphxAI/pdf-reader-mcp (generic), @sylphx/pdf-reader-mcp (npm), @sylphx/pdf-reader-mcp (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps SylphxAI/pdf-reader-mcp (generic), @sylphx/pdf-reader-mcp (npm), @sylphx/pdf-reader-mcp (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| SylphxAI/pdf-reader-mcpgeneric | >=2.2.0 <3.0.1 | 3.0.1 |
| @sylphx/pdf-reader-mcpnpm | >=2.2.0,<3.0.1 | 3.0.1 |
| @sylphx/pdf-reader-mcpnpm | >=2.2.0,<3.0.1 | 3.0.1 |
Published upstream
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 29, 2026
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.
Quoted source text, attributed separately from HOL analysis.