CVE-2026-33213
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRedash 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe get_next_path() function in Redash's authentication module (versions 5.0.2 to 26.3.0) contains an open redirect vulnerability. While the function strips the scheme and netloc from user-supplied next parameters, it fails to normalize multiple leading slashes, allowing crafted URLs like /login?next=////evil.com to redirect authenticated users to attacker-controlled external sites.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 5.0.2, < 26.03.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Redash installation and versionLocate the Redash installation and check its version (typically in a setup.py, package.json, or a VERSION file in the installation directory). Compare this version number to the affected range: 5.0.2 through 26.3.0 inclusive.Affected if The installed version falls within 5.0.2 to 26.3.0 inclusive.
-
Confirm authentication module is in useVerify that Redash is configured with user authentication enabled (check configuration for auth settings such as REDASH_AUTHENTICATION_TYPE, REDASH_LOGIN_URL, or similar authentication-related environment variables or config files).Affected if Authentication is enabled and users can access the login endpoint.
-
Locate the get_next_path functionSearch the Redash source code for the get_next_path function within the authentication module (typically in a file related to authentication such as redash/auth.py or similar).Affected if The get_next_path function exists in the authentication code.
-
Inspect redirect logic for normalization handlingExamine the get_next_path function code to determine if it normalizes multiple leading slashes in the 'next' parameter before performing the redirect (look for URL normalization logic that collapses multiple slashes).Affected if The function does NOT normalize or reject URLs with multiple leading slashes (e.g., ////evil.com) before redirecting.
You are affected if your Redash version is between 5.0.2 and 26.3.0 inclusive, authentication is enabled, and the get_next_path function lacks normalization of multiple leading slashes in the next parameter.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data26.03.1
Normalize multiple leading slashes in the next parameter (e.g., by collapsing multiple slashes to a single slash or rejecting URLs with multiple leading slashes) before performing the redirect, or implement an allowlist of permitted redirect targets.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33213 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33213 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data