{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33213 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-33213 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-33213 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-33213 in the wild and no public exploit code.\n\nAffected product: getredash redash. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33213/ (Markdown: https://insights.sbomify.com/CVE-2026-33213/index.md)","id":"CVE-2026-33213","markdown":"https://insights.sbomify.com/CVE-2026-33213/index.md","name":"CVE-2026-33213","record":{"aliases":["GHSA-rfgc-hc86-pxrv"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Redash data visualization","requires_auth":"none","summary":"Attackers can redirect authenticated users to malicious sites via crafted login URLs, potentially facilitating phishing attacks against Redash users.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"redash","vendor":"redash"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Redash: Open redirect vulnerability in post-login redirect handling","id":"CVE-2026-33213","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Weblate has improper access control for the translation memory API","id":"CVE-2026-33214"},"packages":[],"prev":{"headline":"Weblate: Improper access control for pending tasks in API","id":"CVE-2026-33212"},"products":["redash"],"published":"2026-07-15","related":[{"cvss_score":8.1,"headline":"Insecure default configuration","id":"CVE-2021-41192","kev_date_added":null,"published":"2021-11-23"},{"cvss_score":7.2,"headline":"Server-side request forgery in n/a","id":"CVE-2020-12725","kev_date_added":null,"published":"2020-06-11"},{"cvss_score":6.8,"headline":"Vulnerability in Redash OAuth2 flows due to misuse of state field (should be a nonce)","id":"CVE-2021-43777","kev_date_added":null,"published":"2021-11-23"},{"cvss_score":6.8,"headline":"Server-Side Request Forgery (SSRF) in Redash","id":"CVE-2021-43780","kev_date_added":null,"published":"2021-11-23"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2020-36144","kev_date_added":null,"published":"2021-03-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["getredash"]},"summary":"Attackers can redirect authenticated users to malicious sites via crafted login URLs, potentially facilitating phishing attacks against Redash users.","url":"https://insights.sbomify.com/CVE-2026-33213/"}