Phishing redirect via triple-slash next parameter
Published May 5, 2026 · Updated May 5, 2026
Open redirect in Project Jupyter Jupyter Server 2.17.0 and earlier allows remote attackers to send users to external sites via crafted login URLs. LoginFormHandler._redirect_safe() treats a triple-slash next value as a permitted path and passes it to the redirect response without rejecting its external destination. Exploitation requires a user to follow the crafted login URL, after which the redirect can deliver a phishing site but does not directly compromise the server.
Summary
What happened
Open redirect in Project Jupyter Jupyter Server 2.17.0 and earlier allows remote attackers to send users to external sites via crafted login URLs. LoginFormHandler._redirect_safe() treats a triple-slash next value as a permitted path and passes it to the redirect response without rejecting its external destination. Exploitation requires a user to follow the crafted login URL, after which the redirect can deliver a phishing site but does not directly compromise the server.
The record
- CVE
- CVE-2025-61669
- Published
- May 5, 2026
- Updated
- May 5, 2026
- Vendor
- Project Jupyter
- Product
- Jupyter Server
- Classifications
- CWE-601, T1566.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 5, 2026CVE publishedPublication date reported by the CVE source.
- May 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 2.17.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Triple-slash next parameter proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo