← Back
CVE-2025-30167
Vulnerability in jupyter-core (CVE-2025-30167)
Summary
vulnerability in jupyter-core (CVE-2025-30167). Successful exploitation can lead to full system takeover. Exploitable via ``SYSTEM_CONFIG_PATH``. Mitigation: upgrade to `5.8.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-30167** has been found in jupyter-core.
Attackers can target a specific entry point like ``SYSTEM_CONFIG_PATH`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade jupyter-core to **5.8.1** or later.
If unsure, ask your IT team or search "jupyter-core CVE-2025-30167" on the vendor's site.
CVE-2025-30167 (jupyter-core) — CWE-427 /
Attack vector: local
Attack surface: `SYSTEM_CONFIG_PATH` / `SYSTEM_JUPYTER_PATH`
Patched: `5.8.1` — apply immediately
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-427) exists in jupyter-core. Attackers reach the vulnerable code path via ``SYSTEM_CONFIG_PATH`` without authentication.
📍 Affected scope
jupyter-core — . Attack surface: `SYSTEM_CONFIG_PATH` / `SYSTEM_JUPYTER_PATH`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **5.8.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'jupyter-core' .` 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-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `jupyter-core` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade jupyter-core to 5.8.1ステージング環境で 5.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
jupyter-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.8.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-30167
- advisory https://github.com/advisories/GHSA-33p9-3p43-82vq
- package https://github.com/jupyter/jupyter_core
- package https://pypi.org/project/jupyter-core
- web https://github.com/jupyter/jupyter_core/security/advisories/GHSA-33p9-3p43-82vq
- web https://github.com/jupyter/jupyter_core/commit/5e8965600adda6b416692ce7e85ecb2bd814bd52