CVE-2026-77318

HIGHPre-NVD 7.37.3
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th 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: a secondary CVSS source
Elevated

Also known asEUVD-2026-130405 (ENISA EUVD) · GHSA-24pw-rf5p-mgp7 (GitHub Security Advisories)Source: ENISA EUVD

7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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: 7.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 can enforce MCP_TOKEN on /mcp while leaving the state-changing /api/connect and /api/stop management routes unauthenticated. An unauthenticated network caller can use /api/connect to replace runtime_url and document_url values and their tokens, reset ServerContext, and start a kernel client against attacker-controlled infrastructure, causing the server to send Jupyter API and WebSocket traffic to that backend. The caller can also use /api/stop to stop the current notebook kernel. This boundary failure does not require explicit insecure no-auth mode and occurs outside normal MCP JSON-RPC tool dispatch. This issue is fixed in version 1.0.3.

CVSS
7.3
EG Score
7.3HIGHlow confidence
EG Risk
49
EG Risk 49/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)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.5%
EPSS %ILE
44th
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 (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-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. 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 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 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/c2e98fca2df1bbd608451ec416aaa38a4d246fc5
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 advisoryMentions a patch (unverified)🟡 PoC Available

Unauthenticated management routes can hijack the Jupyter backend in standalone HTTP mode · Advisory · datalayer/jupyter-mcp-server · GitHub

https://github.com/datalayer/jupyter-mcp-server/security/advisories/GHSA-24pw-rf5p-mgp7

Vendor Advisories for CVE-2026-77318(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 6× in last 7d / 6× 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 07:56 UTCOSV refresh
  2. 2026-11-21 16:41 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-11-20 01:40 UTCGHSA enrichmentGHSA-24pw-rf5p-mgp7 · GitHub severity HIGH
  5. 2026-11-19 19:29 UTCEchelonGraph re-scored
  6. 2026-11-19 18:42 UTCEchelonGraph re-scored
  7. 2026-11-19 18:28 UTCEchelonGraph re-scored
  8. 2026-11-19 18:03 UTCENISA EUVD ID recordedEUVD-2026-130405 · Source: ENISA EUVD
  9. 2026-11-19 17:28 UTCEchelonGraph re-scored
  10. 2026-11-19 17:08 UTCEchelonGraph re-scoredFirst assessed: 7.3 HIGH
  11. 2026-11-19 17:07 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-77318?
CVE-2026-77318 is a high-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 can enforce MCP_TOKEN on /mcp while leaving the state-changing /api/connect and /api/stop management routes unauthenticated. An unauthenticated network caller can use /api/connect to…
When was the CVE record for CVE-2026-77318 published?
The CVE record for CVE-2026-77318 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-77318 actively exploited?
CVE-2026-77318 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77318?
CVE-2026-77318 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-77318?
A fix for CVE-2026-77318 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-77318 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-77318?

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