CVE-2026-40110: jupyter-server CORS origin validation bypass via unanchored regex in allow_origin_pat
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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-40110?
CVE-2026-40110 is classified as a high severity vulnerability due to potential unauthorized resource access.
How do I fix CVE-2026-40110?
To fix CVE-2026-40110, upgrade jupyter-server to version 2.18.0 or later.
What software versions are affected by CVE-2026-40110?
CVE-2026-40110 affects jupyter-server versions 2.17.0 and earlier.
What type of vulnerability is CVE-2026-40110?
CVE-2026-40110 is a CORS origin validation bypass vulnerability.
What does the CVE-2026-40110 vulnerability impact?
CVE-2026-40110 impacts the validation of the Origin header in requests to the Jupyter Server backend, leading to possible security bypass.