{"answers":{"affected":"3 open source packages ship an affected version, including jupyter-server. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61669 exists.","fix":"Upgrade jupyter-server to 2.18.0 or later.","what":"CVE-2025-61669 is a medium-severity vulnerability in jupyter-server jupyter_server, published on 5 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-61669 and fix it if it is affected.\n\nWhat it is: CVE-2025-61669 is a medium-severity vulnerability in jupyter-server jupyter_server, published on 5 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61669 exists.\n\nAffected packages and fixed versions:\n- jupyter-server (PyPI): affected all versions; fixed in 2.18.0\n- jupyter-server (PyPI): affected all versions; fixed in 2.18.0\n- jupyter-server (PyPI): affected all versions; fixed in 2.18.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-61669/ (Markdown: https://insights.sbomify.com/CVE-2025-61669/index.md)","id":"CVE-2025-61669","markdown":"https://insights.sbomify.com/CVE-2025-61669/index.md","name":"CVE-2025-61669","record":{"aliases":["CLEANSTART-2026-JD56309","CLEANSTART-2026-ZJ86247","DEBIAN-CVE-2025-61669","GHSA-qh7q-6qm3-653w","PYSEC-2026-67","UBUNTU-CVE-2025-61669"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jupyter Server","requires_auth":"none","summary":"Attackers can redirect users to malicious external domains via the login next parameter, facilitating phishing attacks against Jupyter Server users.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jupyter_server","vendor":"jupyter"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"jupyter_server next parameter open redirect can redirect users to external domains","id":"CVE-2025-61669","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"open_redirect","year":"2025"},"n_packages":3,"n_references":1,"next":{"headline":"Wasmtime has memory leak in C API with `externref` and `anyref` types","id":"CVE-2025-61670"},"packages":[{"ecosystem":"PyPI","fixed":["2.18.0"],"introduced":["0"],"last_affected":[],"package":"jupyter-server","purl":null,"source":"GHSA-qh7q-6qm3-653w"},{"ecosystem":"PyPI","fixed":["2.18.0"],"introduced":["0"],"last_affected":[],"package":"jupyter-server","purl":"pkg:pypi/jupyter-server","source":"GHSA-qh7q-6qm3-653w"},{"ecosystem":"PyPI","fixed":["2.18.0"],"introduced":["0"],"last_affected":[],"package":"jupyter-server","purl":"pkg:pypi/jupyter-server","source":"PYSEC-2026-67"}],"prev":{"headline":"@plone/volto vulnerable to potential DoS by invoking specific URL by anonymous user","id":"CVE-2025-61668"},"products":["jupyter_server"],"published":"2026-05-05","related":[{"cvss_score":9.3,"headline":"Jupyter Server: Stored XSS in `NbconvertFileHandler` / `NbconvertPostHandler` via missing `sandbox` CSP","id":"CVE-2026-44727","kev_date_added":null,"published":"2026-06-22"},{"cvss_score":7.6,"headline":"jupyter-server path traversal allows access to sibling directories sharing root_dir name prefix","id":"CVE-2026-35397","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":7.6,"headline":"jupyter-server CORS origin validation bypass via unanchored regex in allow_origin_pat","id":"CVE-2026-40110","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":7.6,"headline":"jupyter-server authentication cookies remain valid after password reset due to static cookie secret","id":"CVE-2026-40934","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":7.5,"headline":"Jupyter server on Windows discloses Windows user password hash","id":"CVE-2024-35178","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":7.5,"headline":"Sensitive Auth \u0026 Cookie data stored in Jupyter server logs","id":"CVE-2022-24757","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":7.1,"headline":"Known or guessable hidden files may be accessed in Jupyter Server","id":"CVE-2022-29241","kev_date_added":null,"published":"2022-06-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-05","vendors":["jupyter-server"]},"summary":"Attackers can redirect users to malicious external domains via the login next parameter, facilitating phishing attacks against Jupyter Server users.","url":"https://insights.sbomify.com/CVE-2025-61669/"}