Read the docs
TI-2026-74377 Aliases CVE-2026-76083

Server-side request forgery in Redash JSON data source queries

Priority LOW 23CWE-918Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
Information disclosure
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-918 and the CVSS impact.

Summary

Redash from 10.0.0 before 26.9.0 is affected. The JSON data source query runner combines a configured base URL with a user-supplied query URL, so an absolute query URL can point server-side requests (CWE-918) at an arbitrary external origin. A user with execute_query permission can direct these requests to that origin, and configured HTTP Basic Auth credentials are forwarded to it. Private and internal address access stays constrained when REDASH_ENFORCE_PRIVATE_IP_BLOCK is enabled.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00414 35th percentileScored 2026-11-07
Fix Fixed redash (getredash): 26.9.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
getredashredash10.0.0 to before 26.9.026.9.0Patch availableCNA
  • redash Vendorgetredash Affected 10.0.0 to before 26.9.0 Fixed in 26.9.0 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:redash:redash:*:*:*:*:*:*:*:*——getredash
  • cpe:2.3:a:redash:redash:*:*:*:*:*:*:*:* Versions — — ·getredash

Remediation

Upgrade Redash to version 26.9.0, which fixes this issue.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

  • Fix · CNA redash (getredash) Fixed in 26.9.0

Timeline

  1. 2026-10-15 Threatist record created from CVE-2026-76083
  2. 2026-10-16 CISA SSVC decision points changed

References

Other 3

  • TI-2026-74378 Redash DuckDB query runner lets users read and write arbitrary files CVSS 4.0CRITICAL 9.3
  • TI-2026-74373 SQL injection in Redash Query Results parameter substitution CVSS 4.0HIGH 8.7
  • TI-2021-18031 Insecure default configuration CVSS 3.1HIGH 8.1
  • TI-2021-19587 Server-Side Request Forgery (SSRF) in Redash CVSS 3.1HIGH 8.8
  • TI-2020-10116 Havoc Research discovered an authenticated Server-Side Request Forgery (SSRF) via the… CVSS 3.1HIGH 7.2
  • TI-2021-19584 Vulnerability in Redash OAuth2 flows due to misuse of state field (should be a nonce) CVSS 3.1MEDIUM 6.8
See all 8 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences