← Back
CVE-2026-40864
medium
CVSS 5.4
Cross-Site Request Forgery (CSRF) in jupyterhub (CVE-2026-40864)
Summary
vulnerability in jupyterhub (CVE-2026-40864). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `5.4.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-40864** has been found in jupyterhub.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade jupyterhub to **5.4.5** or later.
If unsure, ask your IT team or search "jupyterhub CVE-2026-40864" on the vendor's site.
CVE-2026-40864 (jupyterhub) — CWE-352 / CVSS v3 5.4
Attack vector: remote (network-reachable) / unauthenticated
Patched: `5.4.5` — 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
**CSRF** (CWE-352) exists in jupyterhub.
📍 Affected scope
jupyterhub — .
🔥 Severity
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.4.5**.
🛡️ 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 'jupyterhub' .` 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 'jupyterhub' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `jupyterhub` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade jupyterhub to 5.4.5ステージング環境で 5.4.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
jupyterhub
[{"type":"SEMVER","events":[{"introduced":"4.1.0"},{"fixed":"5.4.5"}]}]
PyPI
jupyterhub
[{"type":"ECOSYSTEM","events":[{"introduced":"4.1.0"},{"fixed":"5.4.5"}]}]
pip
jupyterhub
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.5"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-40864
- package https://github.com/jupyterhub/jupyterhub
- web https://github.com/jupyterhub/jupyterhub/commit/9c5ec277d3cda5a59de2d8c8117efa77bd941127
- web https://github.com/jupyterhub/jupyterhub/security/advisories/GHSA-m68r-v472-jgq9
- web https://github.com/advisories/GHSA-m68r-v472-jgq9