| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-24qx-w28j-9m6p | Jupyter Server has a CORS Origin Validation Bypass via `re.match()` in `allow_origin_pat` (from huntr) |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Wed, 06 May 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 06 May 2026 09:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Jupyter
Jupyter jupyter Server |
|
| Vendors & Products |
Jupyter
Jupyter jupyter Server |
Tue, 05 May 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | jupyter-server CORS origin validation bypass via unanchored regex in allow_origin_pat | |
| Weaknesses | CWE-777 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-06T16:10:34.624Z
Reserved: 2026-04-09T01:41:38.536Z
Link: CVE-2026-40110
Updated: 2026-05-06T16:10:29.740Z
Status : Received
Published: 2026-05-05T22:16:00.663
Modified: 2026-05-05T22:16:00.663
Link: CVE-2026-40110
No data.
OpenCVE Enrichment
Updated: 2026-05-06T09:00:09Z
Github GHSA