CVE-2025-61669 json
jupyter_server next parameter open redirect can redirect users to external domains
published 2026-05-05 6 mo ago modified 2026-10-07 33 d ago also EUVD-2025-209644 , GHSA-qh7q-6qm3-653w , PYSEC-2026-67
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
Jupyter Server is the backend for Jupyter web applications. In jupyter_server versions through 2.17.0, the next query parameter in the login flow is insufficiently validated in `LoginFormHandler._redirect_safe()`, which allows redirects to arbitrary external domains via values such as `///example.com`. An attacker can use a crafted login URL to redirect users to a malicious site and facilitate phishing attacks. This issue is fixed in version 2.18.0.
Patch / fix
- pypi jupyter-server 2.18.0
- jupyter jupyter_server 2.18.0
- jupyter-server Debian 14 2.20.0-1
debian advisories DEBIAN-CVE-2025-61669
- python-jupyter-server openSUSE Tumbleweed 2.18.1-1.1
opensuse advisories openSUSE-SU-2026:10710-1
- jupyter-server Alpine 3.24 2.18.2-r0
alpine advisories ALPINE-CVE-2025-61669
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-61669 updated cvss 6.1
jupyter_server: Jupyter Server: Redirects to arbitrary external domains via insufficient validation of login parameter
-
Red Hat Migration Toolkit for Applications 8 mta/mta-solution-server-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-workbench-jupyter-minimal-cpu-py312-rhel9, rhoai/odh-workbench-jupyter-minimal-cuda-py312-rhel9, rhoai/odh-workbench-jupyter-minimal-rocm-py312-rhel9, rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9, rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9, rhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9, +4 moreaffected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-qh7q-6qm3-653w referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N |
| CNA | 4.0 | 6.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| OSV | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | jupyter-server | <2.18.0 |
2.18.0 |
Affected products
- jupyter-server jupyter_server
Classification
- Weakness
-
- CWE-601 URL Redirection to Untrusted Site
References
-
github.com
/jupyter-server/jupyter_server/security/advisories/GHSA-qh7q-6qm3-653w
exploit, web, vendor-advisory, evidence
-
nvd.nist.gov
/vuln/detail/CVE-2025-61669
advisory
-
github.com
/jupyter-server/jupyter_server
package
-
github.com
/pypa/advisory-database/tree/main/vulns/jupyter-server/PYSEC-2026-67.yaml
web
Sources
- CVE List CVE-2025-61669
- GitHub Advisory GHSA-qh7q-6qm3-653w
- NVD CVE-2025-61669
- OSV PYSEC-2026-67
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.