# CVE-2026-33213: Redash: Open redirect vulnerability in post-login redirect handling

> Attackers can redirect authenticated users to malicious sites via crafted login URLs, potentially facilitating phishing attacks against Redash users.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-rfgc-hc86-pxrv

## What is CVE-2026-33213?

CVE-2026-33213 is a medium-severity vulnerability in getredash redash, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-33213?

It affects 1 product.


Products: Redash Redash.

## How do I fix CVE-2026-33213?

No fix has been published for CVE-2026-33213 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33213 being exploited?

There is no known exploitation of CVE-2026-33213 in the wild and no public exploit code.

## Other vulnerabilities in getredash redash

- [CVE-2021-41192](https://insights.sbomify.com/CVE-2021-41192/): Insecure default configuration (high 8.1)
- [CVE-2020-12725](https://insights.sbomify.com/CVE-2020-12725/): Server-side request forgery in n/a (high 7.2)
- [CVE-2021-43777](https://insights.sbomify.com/CVE-2021-43777/): Vulnerability in Redash OAuth2 flows due to misuse of state field (should be a nonce) (medium 6.8)
- [CVE-2021-43780](https://insights.sbomify.com/CVE-2021-43780/): Server-Side Request Forgery (SSRF) in Redash (medium 6.8)
- [CVE-2020-36144](https://insights.sbomify.com/CVE-2020-36144/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33213 and fix it if it is affected.

What it is: CVE-2026-33213 is a medium-severity vulnerability in getredash redash, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-33213 in the wild and no public exploit code.

Affected product: getredash redash. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33213/ (Markdown: https://insights.sbomify.com/CVE-2026-33213/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33213
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33213
- OSV: https://osv.dev/vulnerability/CVE-2026-33213

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33213/
Summaries are generated and may contain mistakes; the official description above is the record.