CVE-2026-40110

Published: Mag 06, 2026 Last Modified: Mag 06, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 7,6
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: passive
Confidentiality: N/A
Integrity: N/A
Availability: N/A

Description

AI Translation Available

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.

777

Regular Expression without Anchors

Incomplete
Common Consequences
Security Scopes Affected:
Availability Confidentiality Access Control
Potential Impacts:
Bypass Protection Mechanism
Applicable Platforms
All platforms may be affected
View CWE Details
https://github.com/jupyter-server/jupyter_server/commit/057869a327c46730afede3e…
https://github.com/jupyter-server/jupyter_server/commit/49b34392feaa97735b3b777…
https://github.com/jupyter-server/jupyter_server/pull/603
https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-24qx-…