{"items":[{"id":"NVI-00012957","kind":"vulnerability","title":"Parse Server's GraphQL WebSocket endpoint bypasses security middleware","revision":2,"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-p2x3-8689-cwpg","CVE-2026-32594"],"plain_summary":"GitHub lists this reviewed advisory for parse-server, parse-server. 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-60f8703a204b2b8556b19290d64dea14"],"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-06-17T10:36:04.120Z","value":"7.3 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-60f8703a204b2b8556b19290d64dea14"},{"kind":"CVSS","as_of":"2026-06-17T10:36:04.120Z","value":"6.9 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-60f8703a204b2b8556b19290d64dea14"}],"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-1e8e416e9f35c5d9e7c4c13ecf585411","url":"https://github.com/advisories/GHSA-p2x3-8689-cwpg","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-p2x3-8689-cwpg","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T07:24:52.155Z"},{"id":"sr-60f8703a204b2b8556b19290d64dea14","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-32594","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-32594","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T22:34:42.177Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1e8e416e9f35c5d9e7c4c13ecf585411"],"technology":"parse-server","known_exclusions":[],"conditions_summary":"### Impact\n\nAny Parse Server deployment that uses the GraphQL API is affected. The GraphQL WebSocket endpoint for subscriptions does not pass requests through the Express middleware chain that enforces authentication, introspection control, and query complexity limits. An attacker can connect to the WebSocket endpoint and execute GraphQL operations without providing a valid application or API key, access the GraphQL schema via introspection even when public introspection is disabled, and send arbitrarily complex queries that bypass configured complexity limits.\n\n### Patches\n\nThe unfinished GraphQL WebSocket subscription feature has been removed, including the `createSubscriptions` method and the `subscriptions-transport-ws` dependency. GraphQL subscriptions were never functional in Parse Server as the schema did not define any subscription types.\n\n### Workarounds\n\nBlock WebSocket upgrade requests to the GraphQL subscriptions path (by default `/subscriptions`) at the network level, for example using a reverse proxy or load balancer rule.","public_affected_ranges":[">= 9.0.0, < 9.6.0-alpha.14"]},{"certainty":"source_listed","source_ids":["sr-1e8e416e9f35c5d9e7c4c13ecf585411"],"technology":"parse-server","known_exclusions":[],"conditions_summary":"### Impact\n\nAny Parse Server deployment that uses the GraphQL API is affected. The GraphQL WebSocket endpoint for subscriptions does not pass requests through the Express middleware chain that enforces authentication, introspection control, and query complexity limits. An attacker can connect to the WebSocket endpoint and execute GraphQL operations without providing a valid application or API key, access the GraphQL schema via introspection even when public introspection is disabled, and send arbitrarily complex queries that bypass configured complexity limits.\n\n### Patches\n\nThe unfinished GraphQL WebSocket subscription feature has been removed, including the `createSubscriptions` method and the `subscriptions-transport-ws` dependency. GraphQL subscriptions were never functional in Parse Server as the schema did not define any subscription types.\n\n### Workarounds\n\nBlock WebSocket upgrade requests to the GraphQL subscriptions path (by default `/subscriptions`) at the network level, for example using a reverse proxy or load balancer rule.","public_affected_ranges":["< 8.6.40"]}],"null_published_at":"2026-11-07T07:07:42.474Z","source_updated_at":"2026-09-25T14:19:33.000Z","source_disclosed_at":"2026-03-13T20:04:44.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-11-01T07:24:52.155Z"},{"id":"NVI-00012957","kind":"vulnerability","title":"Parse Server's GraphQL WebSocket endpoint bypasses security middleware","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-p2x3-8689-cwpg","CVE-2026-32594"],"plain_summary":"GitHub lists this reviewed advisory for parse-server, parse-server. 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-1e8e416e9f35c5d9e7c4c13ecf585411"],"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":[],"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-1e8e416e9f35c5d9e7c4c13ecf585411","url":"https://github.com/advisories/GHSA-p2x3-8689-cwpg","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-p2x3-8689-cwpg","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T07:24:52.155Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1e8e416e9f35c5d9e7c4c13ecf585411"],"technology":"parse-server","known_exclusions":[],"conditions_summary":"### Impact\n\nAny Parse Server deployment that uses the GraphQL API is affected. The GraphQL WebSocket endpoint for subscriptions does not pass requests through the Express middleware chain that enforces authentication, introspection control, and query complexity limits. An attacker can connect to the WebSocket endpoint and execute GraphQL operations without providing a valid application or API key, access the GraphQL schema via introspection even when public introspection is disabled, and send arbitrarily complex queries that bypass configured complexity limits.\n\n### Patches\n\nThe unfinished GraphQL WebSocket subscription feature has been removed, including the `createSubscriptions` method and the `subscriptions-transport-ws` dependency. GraphQL subscriptions were never functional in Parse Server as the schema did not define any subscription types.\n\n### Workarounds\n\nBlock WebSocket upgrade requests to the GraphQL subscriptions path (by default `/subscriptions`) at the network level, for example using a reverse proxy or load balancer rule.","public_affected_ranges":[">= 9.0.0, < 9.6.0-alpha.14"]},{"certainty":"source_listed","source_ids":["sr-1e8e416e9f35c5d9e7c4c13ecf585411"],"technology":"parse-server","known_exclusions":[],"conditions_summary":"### Impact\n\nAny Parse Server deployment that uses the GraphQL API is affected. The GraphQL WebSocket endpoint for subscriptions does not pass requests through the Express middleware chain that enforces authentication, introspection control, and query complexity limits. An attacker can connect to the WebSocket endpoint and execute GraphQL operations without providing a valid application or API key, access the GraphQL schema via introspection even when public introspection is disabled, and send arbitrarily complex queries that bypass configured complexity limits.\n\n### Patches\n\nThe unfinished GraphQL WebSocket subscription feature has been removed, including the `createSubscriptions` method and the `subscriptions-transport-ws` dependency. GraphQL subscriptions were never functional in Parse Server as the schema did not define any subscription types.\n\n### Workarounds\n\nBlock WebSocket upgrade requests to the GraphQL subscriptions path (by default `/subscriptions`) at the network level, for example using a reverse proxy or load balancer rule.","public_affected_ranges":["< 8.6.40"]}],"null_published_at":"2026-11-01T07:29:12.904Z","source_updated_at":"2026-09-25T14:19:33.000Z","source_disclosed_at":"2026-03-13T20:04:44.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-11-01T07:24:52.155Z"}],"next_cursor":null,"snapshot_revision":"42594"}