Skip to main content
VulnerabilityPublished

CVE-2026-62264: SylphxAI pdf-reader-mcp · Information Exposure

Affects SylphxAI pdf-reader-mcpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 3.0.1 soon.

Data as of 30 Oct 2026, 20:38 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.5
Patch
Available – fixed in 3.0.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade SylphxAI pdf-reader-mcp to 3.0.1.

Affected software

ProductAffectedFixed in
SylphxAIpdf-reader-mcpAffected
  • >=2.2.0 <3.0.1
Fixed in
  • 3.0.1
GitHubsylphxai/pdf-reader-mcppkg:github/sylphxai/pdf-reader-mcpOther threatsAffected
  • =3.0.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade SylphxAI pdf-reader-mcp to version 3.0.1 or later, where this authentication bypass vulnerability is fixed. Until then, avoid enabling the HTTP transport (MCP_TRANSPORT=http) or restrict network access to the server port to trusted clients only. The default stdio transport is not affected. No other mitigations are documented by the vendor.

Description

CVE-2026-62264 is a vulnerability in SylphxAI's pdf-reader-mcp affecting versions 2.2.0 through before 3.0.1. When the HTTP server is enabled via MCP_TRANSPORT=http, the server logs that API key authentication is enabled but does not actually validate the X-API-Key header. This allows unauthenticated clients to access the /mcp endpoint and use PDF reading tools with the permissions of the server process. The default bind address 0.0.0.0 exposes this to any reachable client. URL-based sources can also trigger limited server-side request forgery if private IP allowance is enabled. The issue is fixed in version 3.0.1.

References

Community reviews

Loading reviews…