Vulnerability-Lookup

GHSA-Q344-5V34-GM84

Vulnerability from github – Published: 2026-10-29 16:34 – Updated: 2026-10-29 16:34

Summary

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

Details

Impact

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. Combined with the default bind address of 0.0.0.0 (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 --allow-private-ips is set).

The misleading startup log made the exposure silent: an operator who set MCP_API_KEY reasonably believed the server was protected when it was not.

This affects only the opt-in HTTP transport; the default stdio transport is unaffected.

Patches

Fixed in @sylphx/pdf-reader-mcp@3.0.1. The fix enforces the X-API-Key header with a constant-time comparison (rejecting missing/mismatched keys with HTTP 401), changes the default bind host to 127.0.0.1 (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: MCP_HTTP_HOST=127.0.0.1.
Place a reverse proxy in front that enforces authentication.
Use the default stdio transport instead of HTTP.
Restrict filesystem reach with --allow-dir / MCP_PDF_ALLOWED_DIRS.

Reported privately by novice-22 via responsible disclosure.

Severity

7.5 (High)


                  
                    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@sylphx/pdf-reader-mcp"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.2.0"
            },
            {
              "fixed": "3.0.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-62264"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-200",
      "CWE-287",
      "CWE-306"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-10-29T16:34:35Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "### Impact\n\nWhen `@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.\n\nAs a result, the `/mcp` endpoint accepted **unauthenticated** requests. Combined with the default bind address of `0.0.0.0` (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 `--allow-private-ips` is set).\n\nThe misleading startup log made the exposure silent: an operator who set `MCP_API_KEY` reasonably believed the server was protected when it was not.\n\nThis affects only the opt-in HTTP transport; the default `stdio` transport is unaffected.\n\n### Patches\n\nFixed in `@sylphx/pdf-reader-mcp@3.0.1`. The fix enforces the `X-API-Key` header with a constant-time comparison (rejecting missing/mismatched keys with HTTP 401), changes the default bind host to `127.0.0.1` (loopback), and emits a startup warning when binding a non-loopback host without an API key.\n\n### Workarounds\n\nFor deployments that cannot upgrade immediately:\n\n- Bind to loopback only: `MCP_HTTP_HOST=127.0.0.1`.\n- Place a reverse proxy in front that enforces authentication.\n- Use the default `stdio` transport instead of HTTP.\n- Restrict filesystem reach with `--allow-dir` / `MCP_PDF_ALLOWED_DIRS`.\n\nReported privately by **novice-22** via responsible disclosure.",
  "id": "GHSA-q344-5v34-gm84",
  "modified": "2026-10-29T16:34:35Z",
  "published": "2026-10-29T16:34:35Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/SylphxAI/pdf-reader-mcp/security/advisories/GHSA-q344-5v34-gm84"
    },
    {
      "type": "WEB",
      "url": "https://github.com/SylphxAI/anymd/pull/332"
    },
    {
      "type": "WEB",
      "url": "https://github.com/SylphxAI/anymd/commit/4c35f72862d729301e3912ab8c8317d2828cf4c2"
    },
    {
      "type": "WEB",
      "url": "https://github.com/SylphxAI/anymd/releases/tag/v3.0.1"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/SylphxAI/pdf-reader-mcp"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "@sylphx/pdf-reader-mcp: HTTP transport accepts unauthenticated requests despite a configured MCP_API_KEY"
}

CVE-2026-62264 (GCVE-0-2026-62264)

Vulnerability from cvelistv5 – Published: 2026-10-30 18:32 – Updated: 2026-10-30 18:32

Title

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

Summary

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.

Severity

7.5 (High)


                        
                          CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CWE

CWE-200 - Exposure of Sensitive Information to an Unauthorized Actor
CWE-287 - Improper Authentication
CWE-306 - Missing Authentication for Critical Function

Assigner

GitHub_M CNA under the mitre root

CNA scorecard C 72/100 over 7886 records in the last 180 days details

References

4 references

URL	Tags
https://github.com/SylphxAI/anymd/security/adviso…	x_refsource_CONFIRM
https://github.com/SylphxAI/anymd/pull/332	x_refsource_MISC
https://github.com/SylphxAI/anymd/commit/4c35f728…	x_refsource_MISC
https://github.com/SylphxAI/anymd/tree/v3.0.1	x_refsource_MISC

Impacted products

1 product

Vendor	Product	Version
SylphxAI	pdf-reader-mcp	Affected: >= 2.2.0, < 3.0.1

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "pdf-reader-mcp",
          "vendor": "SylphxAI",
          "versions": [
            {
              "status": "affected",
              "version": "\u003e= 2.2.0, \u003c 3.0.1"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "NONE",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-200",
              "description": "CWE-200: Exposure of Sensitive Information to an Unauthorized Actor",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-287",
              "description": "CWE-287: Improper Authentication",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-306",
              "description": "CWE-306: Missing Authentication for Critical Function",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-30T18:32:18.093Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/SylphxAI/anymd/security/advisories/GHSA-q344-5v34-gm84",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/SylphxAI/anymd/security/advisories/GHSA-q344-5v34-gm84"
        },
        {
          "name": "https://github.com/SylphxAI/anymd/pull/332",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/SylphxAI/anymd/pull/332"
        },
        {
          "name": "https://github.com/SylphxAI/anymd/commit/4c35f72862d729301e3912ab8c8317d2828cf4c2",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/SylphxAI/anymd/commit/4c35f72862d729301e3912ab8c8317d2828cf4c2"
        },
        {
          "name": "https://github.com/SylphxAI/anymd/tree/v3.0.1",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/SylphxAI/anymd/tree/v3.0.1"
        }
      ],
      "source": {
        "advisory": "GHSA-q344-5v34-gm84",
        "discovery": "UNKNOWN"
      },
      "title": "PDF Reader MCP: HTTP transport accepts unauthenticated requests despite a configured MCP_API_KEY"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-62264",
    "datePublished": "2026-10-30T18:32:18.093Z",
    "dateReserved": "2026-07-13T17:09:57.574Z",
    "dateUpdated": "2026-10-30T18:32:18.093Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted