CVE-2026-40110

HIGHNVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 73% 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
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0

A fix is available — apply it.

Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, the Origin header validation uses Python's re.match() to check incoming origins against the allow_origin_pat configuration value. Because re.match() only anchors at the start of the string and does not require a full match, a pattern intended to match only a trusted domain (e.g., trusted.example.com) will also match any origin that begins with that domain followed by additional characters (e.g., trusted.example.com.evil.com). An attacker who controls such a domain can bypass the CORS origin restriction and make cross-origin requests to the Jupyter Server API from an untrusted site. This issue has been fixed in version 2.18.0.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

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
Severity73% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

May 5, 2026

Last Modified

July 24, 2026

Advisory Details (4)

Auto-updated May 5, 2026
Patch available. Sources: github.
github Patch Available

CORS Origin Validation Bypass via `re.match()` in `allow_origin_pat` · Advisory · jupyter-server/jupyter_server · GitHub

https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-24qx-w28j-9m6p
generic

Fix allow_origin_pat property to properly parse regex by havok2063 · Pull Request #603 · jupyter-server/jupyter_server · GitHub

https://github.com/jupyter-server/jupyter_server/pull/603
generic

Move check origin into a util function and add it to websocket (#1630) · jupyter-server/jupyter_server@49b3439 · GitHub

https://github.com/jupyter-server/jupyter_server/commit/49b34392feaa97735b3b777e3baf8f22f2a14ed8
generic

Fix allow_origin_pat to do full matching instead of prefix matching · jupyter-server/jupyter_server@057869a · GitHub

https://github.com/jupyter-server/jupyter_server/commit/057869a327c46730afede3eab0ca2d2e3e74acea

Vendor Advisories for CVE-2026-40110(2)

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 / EcosystemFixed in / PatchReleasedSource
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 rangeFixed inDependents
jupyter-server1.10.2-1 ... 2.9.1-1 (28 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
jupyter-server1.23.3-1 ... 2.9.1-1 (14 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
jupyter-server2.15.0-1, 2.17.0-1, 2.20.0-1, 2.20.0-2, 2.20.0-3——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
jupyter-server2.15.0-1, 2.17.0-12.20.0-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
jupyter-server0.0.0 ... 2.9.1 (155 versions)2.18.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 51× 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 172 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-40110?
CVE-2026-40110 is a high vulnerability published on May 5, 2026. Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, the Origin header validation uses Python's re.match() to check incoming origins against the alloworiginpat configuration value. Because re.match() only anchors at the start of the string and does not require…
When was CVE-2026-40110 disclosed?
CVE-2026-40110 was first published in the National Vulnerability Database on May 5, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40110 actively exploited?
CVE-2026-40110 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.1% of all scored CVEs.
What is the CVSS score of CVE-2026-40110?
CVE-2026-40110 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-40110?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40110, 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-40110

Explore →

Is Your Infrastructure Affected by CVE-2026-40110?

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

Start Free Scan →Browse All CVEs