CVE-2026-77359

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (43rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-130467 (ENISA EUVD) · GHSA-9x8x-crjq-g64h (GitHub Security Advisories)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Jupyter MCP Server is a Model Context Protocol server for Jupyter. Prior to 1.0.3, standalone streamable-http mode validates Host and Origin values for /mcp but does not apply the same browser-origin controls to the state-changing /api/connect and /api/stop management routes. A malicious website can use DNS rebinding so that its hostname resolves to a loopback, LAN, VPN, or published-container MCP listener, then send a browser-shaped request that /api/connect accepts to replace runtime_url and document_url values and start a kernel client against attacker-controlled infrastructure. The attacker can thereby cause Jupyter API and WebSocket traffic to reach that infrastructure and can use /api/stop to stop the current notebook kernel. The default broad bind can increase exposure, but the vulnerability is the missing management-route origin boundary, not a lack of Host validation on /mcp. This issue is fixed in version 1.0.3.

CVSS
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
73
EG Risk 73/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 19, 2026

Last Modified

November 19, 2026

Advisory Details (4)

Auto-updated Nov 19, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Browser DNS rebinding can hijack the Jupyter backend through management routes · Advisory · datalayer/jupyter-mcp-server · GitHub

https://github.com/datalayer/jupyter-mcp-server/security/advisories/GHSA-9x8x-crjq-g64h
GitHub release Patch Available

Release 1.0.3

Patch available: datalayer/jupyter-mcp-server v1.0.3

https://github.com/datalayer/jupyter-mcp-server/releases/tag/v1.0.3
GitHub pull request Patch Available

Protect management routes

Patch available: datalayer/jupyter-mcp-server v1.3.7 (PR #262 merged 2026-07-11)

https://github.com/datalayer/jupyter-mcp-server/pull/262
GitHub commit Patch Available

commit c2e98fca2df1 (datalayer/jupyter-mcp-server)

Patch available: datalayer/jupyter-mcp-server v1.3.7 (contains commit c2e98fca2df1)

https://github.com/datalayer/jupyter-mcp-server/commit/c2e98fca2df1bbd608451ec416aaa38a4

Vendor Advisories for CVE-2026-77359(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipjupyter-mcp-server @ 1.0.3 (fixes <= 1.0.2)—ghsa

These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-22 04:34 UTCEchelonGraph re-scored
  2. 2026-11-22 04:33 UTCGHSA enrichmentGHSA-9x8x-crjq-g64h · GitHub severity CRITICAL
  3. 2026-11-21 16:41 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-11-21 02:32 UTCEchelonGraph re-scored
  5. 2026-11-21 02:32 UTCGHSA enrichmentGHSA-9x8x-crjq-g64h · GitHub severity CRITICAL
  6. 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-11-20 00:51 UTCGHSA enrichmentGHSA-9x8x-crjq-g64h · GitHub severity CRITICAL
  8. 2026-11-19 20:28 UTCEchelonGraph re-scored
  9. 2026-11-19 19:42 UTCEchelonGraph re-scored
  10. 2026-11-19 19:24 UTCEchelonGraph re-scored
  11. 2026-11-19 19:03 UTCENISA EUVD ID recordedEUVD-2026-130467 · Source: ENISA EUVD
  12. 2026-11-19 17:28 UTCEchelonGraph re-scored
  13. 2026-11-19 17:18 UTCEchelonGraph re-scoredFirst assessed: 9.3 CRITICAL
  14. 2026-11-19 17:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-77359?
CVE-2026-77359 is a critical-severity vulnerability; its CVE record was published on November 19, 2026. Jupyter MCP Server is a Model Context Protocol server for Jupyter. Prior to 1.0.3, standalone streamable-http mode validates Host and Origin values for /mcp but does not apply the same browser-origin controls to the state-changing /api/connect and /api/stop management routes. A malicious website…
When was the CVE record for CVE-2026-77359 published?
The CVE record for CVE-2026-77359 was published on November 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 19, 2026; the record at its source may have been updated since.
Is CVE-2026-77359 actively exploited?
CVE-2026-77359 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77359?
CVE-2026-77359 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77359?
A fix for CVE-2026-77359 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-77359 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-77359

Explore →

Is Your Infrastructure Affected by CVE-2026-77359?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.