CVE-2026-42093: high-severity vulnerability in getredash redash
Redash: SQL Injection via Query Results parameterized query substitution
Published
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.7epss 0.7%
exploitation probability
0.7%top 48% of all CVEs
observed exploitation
nono source reports it
Redash is a package for data visualization and sharing. From versions after 8.0.0 until 26.9.0, the Query Results query runner in redash/query_runner/query_results.py accepts param_query_N_{key=value} parameters and passed attacker-controlled values to replace_query_parameters() for raw substitution into a referenced query's SQL. This path bypassed the ParameterizedQuery schema validation used by normal query execution and omitted the is_safe permission check. An authenticated user with at least view-only access to both the Query Results data source and the referenced data source could therefore inject SQL through text parameters and execute it with the referenced data source's privileges. This issue is fixed in version 26.9.0.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Affected products
getredash · redashRelated CVEs — getredash redash
In the same product, most dangerous first.
CVE-2021-41192HIGHInsecure default configurationEPSS 8.1%CVE-2021-43780MEDIUMServer-Side Request Forgery (SSRF) in RedashEPSS 1.0%CVE-2026-77371CRITICALRedash: DuckDB query runner allows arbitrary file read/write via unrestricted external accessEPSS 0.5%CVE-2026-76083MEDIUMRedash: JSON data source query URL can bypass base URL restrictionEPSS 0.4%CVE-2026-33213MEDIUMRedash: Open redirect vulnerability in post-login redirect handlingEPSS 0.3%CVE-2021-43777MEDIUMVulnerability in Redash OAuth2 flows due to misuse of state field (should be a nonce)EPSS 0.3%