ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-62264

@sylphx/pdf-reader-mcp: HTTP transport accepts unauthenticated requests despite a configured MCP_API_KEY

Published Oct 29, 2026 · catalog updated Oct 29, 2026 · @sylphx/pdf-reader-mcp: HTTP transport accepts

Last checked Nov 3, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-62264. EPSS is 0.45%. Act only if a listed version of @sylphx/pdf-reader-mcp: HTTP transport accepts is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (@sylphx/pdf-reader-mcp: HTTP transport accepts).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.45%
Remediation
Version ranges on file
Affected products
npm @sylphx · npm @sylphx/pdf-reader-mcp

### Impact When is run as an HTTP server ( ), it reads the environment variable and logs at startup, but it never validated the header on incoming requests. The key was read into a variable and never enforced on the request path. As a result, the endpoint accepted **unauthenticated** requests. Combined with the default bind address of (all interfaces), any client able to reach the port could invoke every PDF tool and read the contents of any PDF the server process could open anywhere on the host. URL-based sources also enable limited SSRF (private/loopback addresses are blocked by default unless is set). The misleading startup log made the exposure silent: an operator who set reasonably believed the server was protected when it was not. This affects only the opt-in HTTP transport; the default transport is unaffected. ### Patches Fixed in . The fix enforces the header with a constant-time comparison (rejecting missing/mismatched keys with HTTP 401), changes the default bind host to (loopback), and emits a startup warning when binding a non-loopback host without an API key. ### Workarounds For deployments that cannot upgrade immediately: - Bind to loopback only: . - Place a reverse proxy in front that enforces authentication. - Use the default transport instead of HTTP. - Restrict filesystem reach with / . Reported privately by **novice-22** via responsible disclosure.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm @sylphxversion unspecified
  • npm @sylphx/pdf-reader-mcp>= 2.2.0, < 3.0.1

How to fix CVE-2026-62264

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-62264. EPSS is 0.45%. Act only if a listed version of @sylphx/pdf-reader-mcp: HTTP transport accepts is installed.

Which versions are affected?

Compare what you have installed with >= 2.2.0, < 3.0.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-200: Exposure of Sensitive Information; CWE-287: Improper Authentication; CWE-306: Missing Authentication for Critical Function. EPSS 0.45%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 29, 2026 · GitHub Advisory Database

    Detected

    ### Impact When is run as an HTTP server ( ), it reads the environment variable and logs at startup, but it never validated the header on incoming requests. The key was read into a variable and never enforced on the request path. As a result, the endpoint accepted **unauthenticated** requests. Combined with the default bind address of (all interfaces), any client able to reach the port could invok

  2. Oct 29, 2026 · GitHub Advisory Database

    Updated

    ### Impact When is run as an HTTP server ( ), it reads the environment variable and logs at startup, but it never validated the header on incoming requests. The key was read into a variable and never enforced on the request path. As a result, the endpoint accepted **unauthenticated** requests. Combined with the default bind address of (all interfaces), any client able to reach the port could invok

Sources

  • CVE.orgVulnerability recordCVE-2026-62264

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-62264

    30-day exploitation probability 0.45%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-q344-5v34-gm84

    @sylphx/pdf-reader-mcp: HTTP transport accepts unauthenticated requests despite a configured MCP_API_KEY

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-62264

    When @sylphx/pdf-reader-mcp is run as an HTTP server (MCP_TRANSPORT=http), it reads the MCP_API_KEY environment variable and logs API key authentication enabled (X-API-Key header) at startup, but it never validated the X-API-Key header on incoming requests. The key was read into a variable and never enforced on the request path. As a result, the /mcp endpoint accepted unauthenticated requests. Com

    advisories.gitlab.com

References

Freshness

Last verified in this catalog Nov 3, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitLab Advisory DatabaseNov 3, 2026
  • FIRST EPSSOct 31, 2026
  • CVE.orgOct 30, 2026
  • GitHub Advisory DatabaseOct 30, 2026