{"items":[{"id":"NVI-00009131","kind":"vulnerability","title":"@sylphx/pdf-reader-mcp: HTTP transport accepts unauthenticated requests despite a configured MCP_API_KEY","revision":5,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-q344-5v34-gm84","CVE-2026-62264"],"plain_summary":"GitHub lists this reviewed advisory for @sylphx/pdf-reader-mcp. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0df81511c510a132deb36fc8bf0ab22d"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.0.1 for @sylphx/pdf-reader-mcp. Confirm the publisher’s latest guidance.","source_ids":["sr-43f7cb508345e60311bce2aa928c0c47"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-29T16:34:38.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-c23776f5d59775364ee9ca4566287b82"},{"kind":"CVSS","as_of":"2026-11-06T18:18:16.043Z","value":"7.5 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-1998bad2a61ead7e90a7b9dd4f803c10"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.452%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.39284. Missing scores are unknown.","source_id":"sr-0df81511c510a132deb36fc8bf0ab22d"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-c23776f5d59775364ee9ca4566287b82","url":"https://github.com/advisories/GHSA-q344-5v34-gm84","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-q344-5v34-gm84","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:08.420Z"},{"id":"sr-43f7cb508345e60311bce2aa928c0c47","url":"https://github.com/advisories/GHSA-q344-5v34-gm84","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-q344-5v34-gm84","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-01T01:40:53.589Z"},{"id":"sr-1998bad2a61ead7e90a7b9dd4f803c10","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62264","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-62264","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-08T15:07:15.902Z"},{"id":"sr-0df81511c510a132deb36fc8bf0ab22d","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-62264","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.284Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c23776f5d59775364ee9ca4566287b82"],"technology":"@sylphx/pdf-reader-mcp","known_exclusions":[],"conditions_summary":"### 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), change","public_affected_ranges":[">= 2.2.0, < 3.0.1"]},{"certainty":"source_listed","source_ids":["sr-43f7cb508345e60311bce2aa928c0c47"],"technology":"@sylphx/pdf-reader-mcp","known_exclusions":[],"conditions_summary":"### 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), change","public_affected_ranges":["SEMVER: introduced 2.2.0; fixed 3.0.1"]}],"null_published_at":"2026-11-08T19:53:44.031Z","source_updated_at":"2026-10-29T16:34:38.000Z","source_disclosed_at":"2026-10-29T16:34:35.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:56:08.420Z"},{"id":"NVI-00009131","kind":"vulnerability","title":"@sylphx/pdf-reader-mcp: HTTP transport accepts unauthenticated requests despite a configured MCP_API_KEY","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-q344-5v34-gm84","CVE-2026-62264"],"plain_summary":"GitHub lists this reviewed advisory for @sylphx/pdf-reader-mcp. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0df81511c510a132deb36fc8bf0ab22d"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.0.1 for @sylphx/pdf-reader-mcp. Confirm the publisher’s latest guidance.","source_ids":["sr-43f7cb508345e60311bce2aa928c0c47"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-29T16:34:38.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-c23776f5d59775364ee9ca4566287b82"},{"kind":"CVSS","as_of":"2026-10-30T19:39:14.897Z","value":"7.5 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-3e8f343bcca1105c858679cac9f6c15d"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.452%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.39284. Missing scores are unknown.","source_id":"sr-0df81511c510a132deb36fc8bf0ab22d"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-c23776f5d59775364ee9ca4566287b82","url":"https://github.com/advisories/GHSA-q344-5v34-gm84","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-q344-5v34-gm84","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:08.420Z"},{"id":"sr-43f7cb508345e60311bce2aa928c0c47","url":"https://github.com/advisories/GHSA-q344-5v34-gm84","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-q344-5v34-gm84","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-01T01:40:53.589Z"},{"id":"sr-3e8f343bcca1105c858679cac9f6c15d","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62264","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-62264","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-04T02:47:38.696Z"},{"id":"sr-0df81511c510a132deb36fc8bf0ab22d","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-62264","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.284Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c23776f5d59775364ee9ca4566287b82"],"technology":"@sylphx/pdf-reader-mcp","known_exclusions":[],"conditions_summary":"### 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), change","public_affected_ranges":[">= 2.2.0, < 3.0.1"]},{"certainty":"source_listed","source_ids":["sr-43f7cb508345e60311bce2aa928c0c47"],"technology":"@sylphx/pdf-reader-mcp","known_exclusions":[],"conditions_summary":"### 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), change","public_affected_ranges":["SEMVER: introduced 2.2.0; fixed 3.0.1"]}],"null_published_at":"2026-11-04T10:04:35.937Z","source_updated_at":"2026-10-29T16:34:38.000Z","source_disclosed_at":"2026-10-29T16:34:35.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:56:08.420Z"},{"id":"NVI-00009131","kind":"vulnerability","title":"@sylphx/pdf-reader-mcp: HTTP transport accepts unauthenticated requests despite a configured MCP_API_KEY","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-q344-5v34-gm84","CVE-2026-62264"],"plain_summary":"GitHub lists this reviewed advisory for @sylphx/pdf-reader-mcp. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0df81511c510a132deb36fc8bf0ab22d"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.0.1 for @sylphx/pdf-reader-mcp. Confirm the publisher’s latest guidance.","source_ids":["sr-43f7cb508345e60311bce2aa928c0c47"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-29T16:34:38.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-c23776f5d59775364ee9ca4566287b82"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.452%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.39284. Missing scores are unknown.","source_id":"sr-0df81511c510a132deb36fc8bf0ab22d"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-c23776f5d59775364ee9ca4566287b82","url":"https://github.com/advisories/GHSA-q344-5v34-gm84","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-q344-5v34-gm84","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:08.420Z"},{"id":"sr-43f7cb508345e60311bce2aa928c0c47","url":"https://github.com/advisories/GHSA-q344-5v34-gm84","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-q344-5v34-gm84","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-01T01:40:53.589Z"},{"id":"sr-0df81511c510a132deb36fc8bf0ab22d","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-62264","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.284Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c23776f5d59775364ee9ca4566287b82"],"technology":"@sylphx/pdf-reader-mcp","known_exclusions":[],"conditions_summary":"### 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), change","public_affected_ranges":[">= 2.2.0, < 3.0.1"]},{"certainty":"source_listed","source_ids":["sr-43f7cb508345e60311bce2aa928c0c47"],"technology":"@sylphx/pdf-reader-mcp","known_exclusions":[],"conditions_summary":"### 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), change","public_affected_ranges":["SEMVER: introduced 2.2.0; fixed 3.0.1"]}],"null_published_at":"2026-11-03T17:49:18.458Z","source_updated_at":"2026-10-29T16:34:38.000Z","source_disclosed_at":"2026-10-29T16:34:35.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:56:08.420Z"},{"id":"NVI-00009131","kind":"vulnerability","title":"@sylphx/pdf-reader-mcp: HTTP transport accepts unauthenticated requests despite a configured MCP_API_KEY","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-q344-5v34-gm84","CVE-2026-62264"],"plain_summary":"GitHub lists this reviewed advisory for @sylphx/pdf-reader-mcp. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-c23776f5d59775364ee9ca4566287b82"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.0.1 for @sylphx/pdf-reader-mcp. Confirm the publisher’s latest guidance.","source_ids":["sr-43f7cb508345e60311bce2aa928c0c47"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-29T16:34:38.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-c23776f5d59775364ee9ca4566287b82"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-c23776f5d59775364ee9ca4566287b82","url":"https://github.com/advisories/GHSA-q344-5v34-gm84","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-q344-5v34-gm84","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:08.420Z"},{"id":"sr-43f7cb508345e60311bce2aa928c0c47","url":"https://github.com/advisories/GHSA-q344-5v34-gm84","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-q344-5v34-gm84","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-01T01:40:53.589Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c23776f5d59775364ee9ca4566287b82"],"technology":"@sylphx/pdf-reader-mcp","known_exclusions":[],"conditions_summary":"### 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), change","public_affected_ranges":[">= 2.2.0, < 3.0.1"]},{"certainty":"source_listed","source_ids":["sr-43f7cb508345e60311bce2aa928c0c47"],"technology":"@sylphx/pdf-reader-mcp","known_exclusions":[],"conditions_summary":"### 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), change","public_affected_ranges":["SEMVER: introduced 2.2.0; fixed 3.0.1"]}],"null_published_at":"2026-11-01T14:34:14.082Z","source_updated_at":"2026-10-29T16:34:38.000Z","source_disclosed_at":"2026-10-29T16:34:35.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:56:08.420Z"},{"id":"NVI-00009131","kind":"vulnerability","title":"@sylphx/pdf-reader-mcp: HTTP transport accepts unauthenticated requests despite a configured MCP_API_KEY","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-q344-5v34-gm84","CVE-2026-62264"],"plain_summary":"GitHub lists this reviewed advisory for @sylphx/pdf-reader-mcp. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-c23776f5d59775364ee9ca4566287b82"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-29T16:34:38.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-c23776f5d59775364ee9ca4566287b82"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-c23776f5d59775364ee9ca4566287b82","url":"https://github.com/advisories/GHSA-q344-5v34-gm84","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-q344-5v34-gm84","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:08.420Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c23776f5d59775364ee9ca4566287b82"],"technology":"@sylphx/pdf-reader-mcp","known_exclusions":[],"conditions_summary":"### 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), change","public_affected_ranges":[">= 2.2.0, < 3.0.1"]}],"null_published_at":"2026-10-31T22:13:31.285Z","source_updated_at":"2026-10-29T16:34:38.000Z","source_disclosed_at":"2026-10-29T16:34:35.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:56:08.420Z"}],"next_cursor":null,"snapshot_revision":"42594"}