CVE-2026-40110: jupyter_server · Regular Expression Without Anchors
Affects jupyter_serverSource CVE Database V5
Not known to be exploited · CVSS 7.6 High · fixed in 2.18.0 : patch jupyter_server soon.
Data as of 2 Nov 2026, 22:58 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.18.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:L/SC:L/SI:L/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 5 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| jupyter-serverjupyter_server | Affected
| Fixed in– |
PyPIjupyter-serverpkg:pypi/jupyter-serverOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Jupyter Server version 2.18.0. Users should upgrade to version 2.18.0 or later to resolve this vulnerability. Until upgraded, carefully review and restrict the allow_origin_pat configuration to avoid patterns that can be partially matched. Patch status is confirmed fixed in 2.18.0 as per the CVE description and vendor advisory.
Description
Jupyter Server versions 2.17.0 and earlier contain a vulnerability in the Origin header validation logic. The server uses Python's re.match() function with a pattern that is not fully anchored, allowing origins that start with a trusted domain but have additional characters appended to bypass CORS restrictions. This enables an attacker controlling such a domain to make unauthorized cross-origin requests to the Jupyter Server API. The issue is fixed in version 2.18.0.
References
- github.com/jupyter-server/jupyter_server/security/advisories/GHSA-24qx-w28j-9m6p (opens in a new tab)
- github.com/jupyter-server/jupyter_server/pull/603 (opens in a new tab)
- github.com/jupyter-server/jupyter_server/commit/057869a327c46730afede3eab0ca2d2e3e74acea (opens in a new tab)
- github.com/jupyter-server/jupyter_server/commit/49b34392feaa97735b3b777e3baf8f22f2a14ed8 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-40110 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2466912 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-40110.json (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:43038 (opens in a new tab)