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.2%, top 87% 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.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.4(medium)
EPSS
13.3%
KEV
Not listed

Published

June 18, 2026

Last Modified

June 30, 2026

Advisory Details (2)

Auto-updated Jun 22, 2026
Patch available. Sources: github_commit, github.
github Patch Available

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(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
jupyter-server0.0.0 ... 2.9.1 (159 versions)2.20.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 53× 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.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 15:08 UTCEG score recompute
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-05 13:19 UTCEG score recompute
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 11:33 UTCEG score recompute
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-03 09:47 UTCEG score recompute
  9. 2026-07-02 08:00 UTCEG score recompute
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-07-01 06:15 UTCEG score recompute
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 04:29 UTCEG score recompute
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 02:43 UTCEG score recompute
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 00:57 UTCEG score recompute
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 23:10 UTCEG score recompute▼ 3.90
  23. 2026-06-26 19:41 UTCNVD updateCVSS v3 → 5.4 · severity → MEDIUM
  24. 2026-06-26 19:15 UTCEG score recompute
  25. 2026-06-26 15:21 UTCEG score recompute
Show 28 more
  1. 2026-06-26 11:26 UTCEG score recompute
  2. 2026-06-26 04:30 UTCEG score recompute
  3. 2026-06-26 00:35 UTCEG score recompute
  4. 2026-06-25 20:39 UTCEG score recompute
  5. 2026-06-25 16:44 UTCEG score recompute
  6. 2026-06-25 13:49 UTCEPSS rescore
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-25 12:49 UTCEG score recompute
  9. 2026-06-25 08:54 UTCEG score recompute
  10. 2026-06-25 04:59 UTCEG score recompute
  11. 2026-06-25 01:03 UTCEG score recompute
  12. 2026-06-24 21:07 UTCEG score recompute
  13. 2026-06-24 17:13 UTCEG score recompute
  14. 2026-06-24 14:05 UTCEPSS rescore
  15. 2026-06-24 13:13 UTCEG score recompute
  16. 2026-06-24 09:17 UTCEG score recompute
  17. 2026-06-24 05:21 UTCEG score recompute
  18. 2026-06-24 01:15 UTCEG score recompute
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-23 21:19 UTCEG score recompute
  21. 2026-06-23 17:25 UTCEG score recompute
  22. 2026-06-23 13:27 UTCEG score recompute
  23. 2026-06-23 09:33 UTCEG score recompute
  24. 2026-06-23 05:37 UTCEG score recompute
  25. 2026-06-23 01:40 UTCEG score recompute
  26. 2026-06-22 21:40 UTCEG score recompute▲ 9.30
  27. 2026-06-22 21:37 UTCNVD updateCVSS v3 → 9.3 · CVSS v4 → 9.3
  28. 2026-06-18 15:08 UTCEG score recompute

Related CVEs(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 in the National Vulnerability Database on June 18, 2026, with the most recent update on June 30, 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 13.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44727, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs