Skip to content

AAK-MCP-PDFREADER-CVE-2026-62264-001: PDF Reader MCP 2.2.0 to 3.0.0: the HTTP transport never checks the configured API key

Severity
HIGH
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
PdfReaderMcpHttpApiKeyUnchecked

What it detects

PDF Reader MCP (npm @sylphx/pdf-reader-mcp; SylphxAI/pdf-reader-mcp, now SylphxAI/anymd) is an MCP server that reads PDF files. From 2.2.0, setting MCP_TRANSPORT=http starts an HTTP server on /mcp, bound to 0.0.0.0 by default. Before 3.0.1 the server read MCP_API_KEY and logged that X-API-Key authentication was enabled, but never passed the key to the transport or checked the header, so any client that could reach the port could call every PDF tool and read any PDF the server process can open, and URL sources gave a limited server-side request forgery (CVE-2026-62264, CVSS 3.1 7.5, CWE-306/CWE-287, GHSA-q344-5v34-gm84). The default stdio transport is not affected. Checked in the published dist/index.js: 2.1.0 has no HTTP transport, 2.2.0 and 3.0.0 only log the key, and 3.0.1 rejects a missing or wrong X-API-Key with 401 and binds 127.0.0.1 by default.

How to fix

Upgrade @sylphx/pdf-reader-mcp to 3.0.1 or later and pin it, or move to @sylphx/anymd, which the package now aliases. Until then run it over stdio, or bind MCP_HTTP_HOST=127.0.0.1 and keep the port behind an authenticating proxy: on an affected release MCP_API_KEY protects nothing.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-PDFREADER-CVE-2026-62264-001

Limitations

Reports @sylphx/pdf-reader-mcp from 2.2.0 below 3.0.1 where a package.json, lockfile or MCP config states the version, reporting a range that admits an affected version. It reads the version, not the transport: a server run over stdio, the default, is reported too, and MCP_TRANSPORT, MCP_HTTP_HOST and MCP_API_KEY in an MCP config's env are not read. latest was 8.5.11 on 2026-11-11, an alias that runs anymd, and states no version, so an unversioned npx @sylphx/pdf-reader-mcp launch, or a config that runs a global install by its bare name, is not reported. @sylphx/anymd first shipped at 7.0.0, after the fix, and is not read; PyPI's pdf-reader-mcp (zixma13/pdf-reader-mcp) is another project and is not matched. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

References

  • CVE: CVE-2026-62264
  • OWASP MCP Top 10: MCP07:2025 (Insufficient Authentication & Authorization), MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering)
  • OWASP Agentic Top 10: ASI03 (Identity and Privilege Abuse), ASI04 (Agentic Supply Chain Vulnerabilities)
  • Adversa AI MCP Top 25 (AAK-defined ids): ADV-AUTH-01 (Missing Authentication), ADV-SUPPLY-08 (MCP-Specific Vuln)
  • CSA AI Controls Matrix (AICM): IAM-01, STA-08

All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-PDFREADER-CVE-2026-62264-001.md: the page then shows that text, with the registry reference appended under it.