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.
CVE-2026-33213
This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.1
- EG Score
- 6.1(medium)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity61% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 7.5%
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (2)
Auto-updated Jul 15, 2026Open redirect vulnerability in post-login redirect handling · Advisory · getredash/redash · GitHub
https://github.com/getredash/redash/security/advisories/GHSA-rfgc-hc86-pxrvcommit 9e66f81673c4 (getredash/redash)
Fix landed in getredash/redash commit 9e66f81673c4 — awaiting tagged release
https://github.com/getredash/redash/commit/9e66f81673c482d9ae6c425afe009644114605d0Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:09 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 14:51 UTCEG score recompute
- 2026-07-15 14:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-601
Frequently asked(5)
What is CVE-2026-33213?
When was CVE-2026-33213 disclosed?
Is CVE-2026-33213 actively exploited?
What is the CVSS score of CVE-2026-33213?
How do I remediate CVE-2026-33213?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-33213
Is Your Infrastructure Affected by CVE-2026-33213?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.