← Back
CVE-2026-40110
high
CVSS 7.3
Vulnerability in jupyter-server (CVE-2026-40110)
Summary
vulnerability in jupyter-server (CVE-2026-40110). Confidential information can be exposed externally. Exploitable via ``allow_origin_pat``. Mitigation: upgrade to `057869a327c46730afede3eab0ca2d2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-40110** has been found in jupyter-server.
Attackers can target a specific entry point like ``allow_origin_pat`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.3/10.
What to do: upgrade jupyter-server to **057869a327c46730afede3eab0ca2d2** or later.
If unsure, ask your IT team or search "jupyter-server CVE-2026-40110" on the vendor's site.
CVE-2026-40110 (jupyter-server) — CWE-777 / CVSS v3 7.3
Attack vector: remote (network-reachable)
Attack surface: `allow_origin_pat` / `trusted.example.com`
Patched: `057869a327c46730afede3eab0ca2d2` — apply immediately
Workaround: Wrap your `allow_origin_pat` value with `^` and `$`
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-777) exists in jupyter-server. Attackers reach the vulnerable code path via ``allow_origin_pat`` without authentication.
📍 Affected scope
jupyter-server — . Attack surface: `allow_origin_pat` / `trusted.example.com`.
🔥 Severity
Severity: High (CVSS 7.3/10). Confidential information can be exposed externally
🔧 How to fix
Update to **057869a327c46730afede3eab0ca2d2**.
🛡️ Workaround
Workaround: Wrap your `allow_origin_pat` value with `^` and `$`
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'jupyter-server' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'jupyter-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `jupyter-server` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Wrap your `allow_origin_pat` value with `^` and `$`パッチが適用されるまでの応急処置として、Wrap your `allow_origin_pat` value with `^` and `$` を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade jupyter-server to 057869a327c46730afede3eab0ca2d2ステージング環境で 057869a327c46730afede3eab0ca2d2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
jupyter-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.18.0"}]}]
PyPI
jupyter-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.18.0"}]}]
References
- issue [email protected]
- package https://github.com/jupyter-server/jupyter_server
- patch [email protected]
- patch [email protected]
- patch [email protected]
- web https://nvd.nist.gov/vuln/detail/CVE-2026-40110
- web https://github.com/advisories/GHSA-24qx-w28j-9m6p
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c