CVEvulnerability
CVE-2026-62264
Exploitation and prioritisation
- EPSS
- 0.45% chance of exploitation in the next 30 days · in the top 60.7% of all CVEs (2026-11-03)
- EU Vulnerability Database
- EUVD-2026-114317
Affected packages
| Ecosystem | Package | Vulnerable | Fixed in | Advisory |
|---|---|---|---|---|
| npm | @sylphx/pdf-reader-mcp | >= 2.2.0, < 3.0.1 | 3.0.1 | GHSA-q344-5v34-gm84 |
- Status
- Deferred
- Published
- 2026-10-30
- Last modified
- 2026-10-30
- Assigner
- [email protected]
- CVSS 3.1 ([email protected])
- 7.5 HIGH — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Weaknesses
- CWE-200, CWE-287, CWE-306
Description
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.
Related
Weakness · CWE (3)
Referenced by GitHub Advisory · alias (1)
- GHSA-q344-5v34-gm84 @sylphx/pdf-reader-mcp: HTTP transport accepts unauthenticated requests despite a configured MCP_API_KEY advisory · npm