Redash: Open redirect vulnerability in post-login redirect handling
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-601.
Summary
Redash is a package for data visualization and sharing. From 5.0.2 to 26.3.0, the get_next_path() function in Redash's authentication module stripped the scheme and netloc from user-supplied next parameters but did not normalize multiple leading slashes, allowing a crafted login URL such as /login?next=////evil.com to redirect users to an external attacker-controlled site after authentication.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-33213
References
More getredash Redash vulnerabilities
- TI-2021-18031 Insecure default configuration CVSS 3.1HIGH 8.1
- TI-2021-19587 Server-Side Request Forgery (SSRF) in Redash CVSS 3.1HIGH 8.8
- TI-2020-10116 Havoc Research discovered an authenticated Server-Side Request Forgery (SSRF) via the… CVSS 3.1HIGH 7.2
- TI-2021-19584 Vulnerability in Redash OAuth2 flows due to misuse of state field (should be a nonce) CVSS 3.1MEDIUM 6.8
- TI-2020-18468 Redash 8.0.0 is affected by LDAP Injection. CVSS 3.1MEDIUM 5.3
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences