Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

Jupyter Server uses re.match() to validate the Origin header against the allow_origin_pat configuration.

Since re.match() only anchors at the start of the string, an attacker who controls a domain like http://trusted.example.com.evil.com/ passes validation against a pattern intended to match only trusted.example.com.

Impact

<=2.17.0

Patches

057869a327c46730afede3eab0ca2d2e3e74acea, 49b34392feaa97735b3b777e3baf8f22f2a14ed8

Workarounds

Wrap your allow_origin_pat value with ^ and $

References

https://github.com/jupyter-server/jupyter_server/pull/603
https://docs.python.org/3/library/re.html#re.fullmatch
https://docs.python.org/3/library/re.html#re.match

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

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-625 / 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-625) exists in jupyter-server. Attackers reach the vulnerable code path via allow_origin_pat.

📍 Affected scope

Check the vendor advisory for the affected versions of 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'jupyter-server' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で jupyter-server を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Wrap your `allow_origin_pat` value with `^` and `$`

    パッチが適用されるまでの応急処置として、Wrap your allow_origin_pat value with ^ and $ を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade jupyter-server to 057869a327c46730afede3eab0ca2d2

    ステージング環境で 057869a327c46730afede3eab0ca2d2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

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"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details