CVE-2026-76083: medium-severity vulnerability in getredash redash
Redash: JSON data source query URL can bypass base URL restriction
Published · Updated
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.9epss 0.4%
exploitation probability
0.4%top 66% of all CVEs
observed exploitation
nono source reports it
Redash is a package for data visualization and sharing. From 10.0.0 until 26.9.0, the JSON data source query runner in redash/query_runner/json_ds.py used _get_all_results() to combine its configured base_url with a user-supplied query URL by using urljoin. An absolute query URL replaced the configured base URL instead of remaining under it, allowing a user with execute_query permission to direct a server-side request to an arbitrary external origin. When HTTP Basic Auth was configured for the data source, the request also forwarded those credentials to the selected origin. Private and internal address access remained constrained when REDASH_ENFORCE_PRIVATE_IP_BLOCK was enabled. This issue is fixed in version 26.9.0.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/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-42093HIGHRedash: SQL Injection via Query Results parameterized query substitutionEPSS 0.7%CVE-2026-77371CRITICALRedash: DuckDB query runner allows arbitrary file read/write via unrestricted external accessEPSS 0.5%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%