getredash Redash up to 26.3.0 Authentication get_next_path Next redirect

Summaryinfo

A vulnerability has been found in getredash Redash up to 26.3.0 and classified as problematic. This affects the function get_next_path of the component Authentication Module. The manipulation of the argument Next leads to redirect. This vulnerability is uniquely identified as CVE-2026-33213. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in getredash Redash up to 26.3.0. It has been rated as problematic. This issue affects the function get_next_path of the component Authentication Module. The manipulation of the argument next with an unknown input leads to a redirect vulnerability. Using CWE to declare the problem leads to CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. Impacted is integrity. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-33213 since 03/18/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/15/2026). MITRE ATT&CK project uses the attack technique T1204.001 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• getredash

Name

• Redash

Version

• 26.0
• 26.1
• 26.2
• 26.3.0

Website

• Product: https://github.com/getredash/redash/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion