Quick answers
- Is CVE-2026-42093 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42093 being exploited in the wild.
- How severe is CVE-2026-42093?
- Informational severity, published 14 October 2026.
- Which products and versions are affected?
- Redash after 8.0.0 through 26.8.x.
- Is there a fix for CVE-2026-42093?
- Yes: fixed in 26.9.0. Until then: Restrict view-only user access to data sources and the Query Results data source until upgrading to 26.9.0. Audit query parameter usage and monitor for suspicious parameterized query execution patterns. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42093 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-42093?
- Check whether you run Redash at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 26.9.0
Restrict view-only user access to data sources and the Query Results data source until upgrading to 26.9.0. Audit query parameter usage and monitor for suspicious parameterized query execution patterns.
Technical details
The Query Results query runner in redash/query_runner/query_results.py accepted param_query_N_{key=value} parameters that were passed directly to replace_query_parameters() for raw SQL substitution, bypassing the ParameterizedQuery schema validation and omitting the is_safe permission check. An authenticated attacker with view-only access to both data sources could inject SQL through text parameters. The fix enforces ParameterizedQuery.apply() validation and requires full data source access when referenced queries have text parameters.
Affected products
- Redash Redash after 8.0.0 through 26.8.x
Timeline
- 2026-10-14: disclosed
- 2026-09-24: patched: Fixed in v26.9.0