CVE-2026-44727

MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 63% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Jupyter Server is the backend for Jupyter web applications. Prior to 2.20, the nbconvert HTTP handlers in jupyter_server render user-authored notebook HTML under the Jupyter origin without a sandbox directive in their Content-Security-Policy. Combined with nbconvert.HTMLExporter's default non-sanitizing behavior, a notebook carrying an HTML payload in a display_data output triggers stored XSS with cookie access, full /api/* authority, and kernel RCE. This vulnerability is fixed in 2.20.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

Published

June 18, 2026

Last Modified

August 28, 2026

Advisory Details (2)

Auto-updated Jun 22, 2026
Patch available. Sources: github_commit, github.
githubMentions a patch (unverified)

Stored XSS in `NbconvertFileHandler` / `NbconvertPostHandler` via missing `sandbox` CSP · Advisory · jupyter-server/jupyter_server · GitHub

Affected: v2.20.0, commit

https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-fcw5-x6j4-ccmp
github_commit Patch Available

commit 6cbee8d65e71 (jupyter-server/jupyter_server)

Patch available: jupyter-server/jupyter_server v2.20.0 (contains commit 6cbee8d65e71)

https://github.com/jupyter-server/jupyter_server/commit/6cbee8d65e71abac851c4492fea987ad080580bd

Vendor Advisories for CVE-2026-44727(4)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
redhatmta/mta-solution-server-rhel9:17841098832026-07-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
jupyter-server1.10.2-1 ... 2.9.1-1 (28 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jupyter-server1.23.3-1 ... 2.9.1-1 (14 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jupyter-server2.15.0-1, 2.17.0-1, 2.20.0-1, 2.20.0-2, 2.20.0-3
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jupyter-server2.15.0-1, 2.17.0-1
  • every version up to 2.20.0-1: fixed in 2.20.0-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
jupyter-server0.0.0 ... 2.9.1 (159 versions)
  • every version up to 2.20.0: fixed in 2.20.0
—

Weakness Classification(2)

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

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 169 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-02 16:13 UTCOSV refresh
  10. 2026-10-02 16:13 UTCOSV refresh
  11. 2026-10-02 16:13 UTCOSV refresh
  12. 2026-10-02 16:12 UTCOSV refresh
  13. 2026-10-02 16:12 UTCOSV refresh
  14. 2026-10-02 16:12 UTCOSV refresh
  15. 2026-10-01 19:50 UTCEPSS rescore
  16. 2026-09-30 15:03 UTCEPSS rescore
  17. 2026-09-27 13:48 UTCEPSS rescore
  18. 2026-09-26 15:58 UTCEPSS rescore
  19. 2026-09-23 17:53 UTCEPSS rescore
  20. 2026-09-20 20:15 UTCEPSS rescore
  21. 2026-09-18 19:28 UTCEPSS rescore
  22. 2026-09-17 19:31 UTCEPSS rescore
  23. 2026-09-16 14:08 UTCEPSS rescore
  24. 2026-09-16 05:15 UTCEPSS rescore
  25. 2026-09-13 16:47 UTCEPSS rescore
Show 75 more
  1. 2026-09-13 13:56 UTCEG score recompute
  2. 2026-09-13 13:56 UTCVendor advisory
  3. 2026-09-12 15:01 UTCEPSS rescore
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-08-30 21:09 UTCEG score recompute
  14. 2026-08-30 21:09 UTCVendor advisory
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-28 16:46 UTCVendor advisory
  19. 2026-08-28 15:59 UTCEG score recompute
  20. 2026-08-28 15:59 UTCVendor advisory
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-25 07:06 UTCEG score recompute
  25. 2026-08-25 07:06 UTCVendor advisory
  26. 2026-08-24 05:12 UTCVendor advisory
  27. 2026-08-23 01:13 UTCEG score recompute
  28. 2026-08-23 01:13 UTCVendor advisory
  29. 2026-08-23 00:19 UTCEPSS rescore
  30. 2026-08-21 23:49 UTCEPSS rescore
  31. 2026-08-21 11:53 UTCEG score recompute
  32. 2026-08-21 11:53 UTCVendor advisory
  33. 2026-08-20 22:55 UTCEPSS rescore
  34. 2026-08-20 09:45 UTCEG score recompute
  35. 2026-08-20 09:45 UTCVendor advisory
  36. 2026-08-19 17:04 UTCEPSS rescore
  37. 2026-08-19 07:59 UTCEG score recompute
  38. 2026-08-19 07:59 UTCVendor advisory
  39. 2026-08-18 13:48 UTCEPSS rescore
  40. 2026-08-17 13:47 UTCEPSS rescore
  41. 2026-08-17 13:40 UTCEG score recompute
  42. 2026-08-17 13:40 UTCVendor advisory
  43. 2026-08-16 14:56 UTCEPSS rescore
  44. 2026-08-16 11:54 UTCEG score recompute
  45. 2026-08-16 11:54 UTCVendor advisory
  46. 2026-08-16 02:14 UTCEPSS rescore
  47. 2026-08-15 10:09 UTCEG score recompute
  48. 2026-08-15 10:09 UTCVendor advisory
  49. 2026-08-15 01:30 UTCEPSS rescore
  50. 2026-08-14 08:23 UTCEG score recompute
  51. 2026-08-14 08:23 UTCVendor advisory
  52. 2026-08-13 22:00 UTCEPSS rescore
  53. 2026-08-13 06:38 UTCEG score recompute
  54. 2026-08-13 06:38 UTCVendor advisory
  55. 2026-08-12 13:51 UTCEPSS rescore
  56. 2026-08-12 04:52 UTCEG score recompute
  57. 2026-08-12 04:52 UTCVendor advisory
  58. 2026-08-11 02:56 UTCEG score recompute
  59. 2026-08-11 02:56 UTCVendor advisory
  60. 2026-08-11 00:00 UTCEPSS rescore
  61. 2026-08-10 01:10 UTCEG score recompute
  62. 2026-08-10 01:10 UTCVendor advisory
  63. 2026-08-09 13:46 UTCEPSS rescore
  64. 2026-08-08 23:25 UTCEG score recompute
  65. 2026-08-08 23:25 UTCVendor advisory
  66. 2026-08-08 16:37 UTCEPSS rescore
  67. 2026-08-07 21:39 UTCEG score recompute
  68. 2026-08-07 21:39 UTCVendor advisory
  69. 2026-08-06 19:53 UTCEG score recompute
  70. 2026-08-06 19:53 UTCVendor advisory
  71. 2026-08-06 13:46 UTCEPSS rescore
  72. 2026-08-05 19:17 UTCEPSS rescore
  73. 2026-08-05 18:07 UTCVendor advisory
  74. 2026-08-04 16:09 UTCEG score recompute
  75. 2026-08-04 16:09 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44727?
CVE-2026-44727 is a medium vulnerability published on June 18, 2026. Jupyter Server is the backend for Jupyter web applications. Prior to 2.20, the nbconvert HTTP handlers in jupyterserver render user-authored notebook HTML under the Jupyter origin without a sandbox directive in their Content-Security-Policy. Combined with nbconvert.HTMLExporter's default…
When was CVE-2026-44727 disclosed?
CVE-2026-44727 was first published on June 18, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44727 actively exploited?
CVE-2026-44727 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44727?
CVE-2026-44727 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-44727?
A fix for CVE-2026-44727 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44727 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44727

Explore →

Is Your Infrastructure Affected by CVE-2026-44727?

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

Book a Demo →Browse All CVEs