CVE-2026-62264

PDF Reader MCP: HTTP transport accepts unauthenticated requests despite a configured MCP_API_KEY

Published Oct 30, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

PDF Reader MCP is a server that supports PDF document processing. In vulnerable configurations, the HTTP transport accepts requests without validating the X-API-Key header, despite startup logs indicating authentication is enabled. This flaw allows an attacker to invoke any PDF tool and retrieve the contents of PDFs that the server process can access, leading to unauthorized disclosure of potentially sensitive documents. The weakness represents a classic authentication bypass (CWE-287) and results in information disclosure (CWE-200). In addition, the open `/mcp` endpoint can be used for limited server‑side request forgery when source URLs are supplied. The attack surface is narrow: the server must be exposed on an accessible network interface, and the client must know the service endpoint.

Affected Systems

The affected vendor is SylphxAI, with the product pdf‑reader‑mcp. Versions starting at 2.2.0 up to, but not including, 3.0.1 contain the vulnerability. Version 3.0.1 and later include a fix that properly validates the X‑API‑Key header when the HTTP server is enabled.

Risk and Exploitability

The product carries a CVSS score of 7.5, indicating a high severity. The EPSS score is not available, so the current probability of exploitation cannot be quantified, but the flaw is non‑trivial and the server may be reachable on the default 0.0.0.0 bind address. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Attackers who can reach the affected service can read arbitrary PDF files and induce limited server‑side request forgery if URLs are supplied; there are no special preconditions beyond network access to the open port.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade SylphxAI pdf‑reader‑mcp to version 3.0.1 or later.
  • If an upgrade is not immediately possible, bind the HTTP server to localhost or use a firewall to limit inbound traffic to the host only.
  • As an interim precaution, disable the HTTP transport by setting MCP_TRANSPORT to a non‑HTTP value or removing it from the configuration.

Generated by OpenCVE AI on October 30, 2026 at 19:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-q344-5v34-gm84 @sylphx/pdf-reader-mcp: HTTP transport accepts unauthenticated requests despite a configured MCP_API_KEY
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Sylphxai
Sylphxai pdf-reader-mcp
Vendors & Products Sylphxai
Sylphxai pdf-reader-mcp
Type Values Removed Values Added
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.
Title PDF Reader MCP: HTTP transport accepts unauthenticated requests despite a configured MCP_API_KEY
Weaknesses CWE-200
CWE-287
CWE-306
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-287

    Improper Authentication

  • CWE-306

    Missing Authentication for Critical Function

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 6, 2026, 5:26 PM
Reserved
Jul 13, 2026, 5:09 PM
Status
Deferred
Published
Oct 30, 2026, 7:18 PM
Modified
Nov 6, 2026, 6:18 PM