CVE-2026-77359
validatedZero produced an exploit or a check.description
Standalone streamable HTTP deployments of jupyter-mcp-server before 1.0.3 do not consistently enforce browser-origin checks on management endpoints. A malicious website may, through DNS rebinding, alter connection targets and cause Jupyter traffic to reach attacker-controlled infrastructure or stop an active notebook kernel when it can reach the MCP listener.
mitigation
Upgrade jupyter-mcp-server to version 1.0.3 or later. Restrict network exposure of the MCP listener, especially avoiding broad binds where they are not required.
outcome
Check only, differential: the check fires on the vulnerable build and is silent on the patched one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-11-19 17:03Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-77359
{ "etk_id": "ETK-2026-4953", "cve_id": "CVE-2026-77359", "display_id": "CVE-2026-77359", "ghsa_id": null, "euvd_id": null, "status": "published", "anchor_state": "anchored", "title": "Missing origin checks in jupyter-mcp-server management routes", "summary": "Standalone streamable HTTP deployments of jupyter-mcp-server before 1.0.3 do not consistently enforce browser-origin checks on management endpoints. A malicious website may, through DNS rebinding, alter connection targets and cause Jupyter traffic to reach attacker-controlled infrastructure or stop an active notebook kernel when it can reach the MCP listener.", "mitigation": "Upgrade jupyter-mcp-server to version 1.0.3 or later. Restrict network exposure of the MCP listener, especially avoiding broad binds where they are not required.", "vendor": "datalayer", "product": "jupyter-mcp-server", "affected": [ { "affected_notes": [], "affected_ranges": [ "<= 1.0.2" ], "ecosystem": "pip", "fixed_versions": [], "package_name": "jupyter-mcp-server", "purl": "pkg:pypi/jupyter-mcp-server" } ], "cwes": [ 350 ], "cvss_score": 9.3, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:H/SI:H/SA:H", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "deterministic", "check": true, "check_confidence_basis": "differential", "exploit": false, "pipeline_minutes": 11.11366395, "t0_at": "2026-11-19T17:03:41.160000+00:00", "signals": { "check": { "at": "2026-11-19T17:43:58.430263+00:00", "days": 0.027977665081018517, "is_lower_bound": false, "measured_at": "2026-11-19T17:03:41.160000+00:00", "url": null }, "trigger_signal": { "at": "2026-11-19T17:03:41.160000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-11-19T17:03:41.160000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-77359" } } }
published 2026-11-19 17:32Z
last change 2026-11-19 17:57Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.