CVE-2026-76083

Awaiting Analysis Awaiting Analysis - Queue

Server-Side Request Forgery in Redash JSON Data Source

Publication date: 2026-10-14

Last updated on: 2026-10-15

Assigner: GitHub, Inc.

Description

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-14

Last Modified

2026-10-15

Generated

2026-10-19

AI Q&A

2026-10-15

EPSS Evaluated

2026-10-18

NVD

CVE-2026-76083

EUVD

EUVD-2026-101516

Affected Vendors & Products

Vendor	Product	Version / Range
getredash	redash	>= 10.0.0, < 26.9.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-918	The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

Executive Summary

CVE-2026-76083 is a Server-Side Request Forgery (SSRF) vulnerability in Redash versions 10.0.0 to 26.9.0. It occurs in the JSON data source query runner where a user-supplied absolute URL replaces the configured base URL entirely. This allows authenticated users with execute_query permission to send server-side requests to arbitrary external hosts, potentially exposing HTTP Basic Auth credentials if configured in the data source.

The vulnerability was fixed in version 26.9.0 by adding hostname validation to ensure the resolved URL stays within the base URL's origin.

Detection Guidance

Check Redash versions between 10.0.0 and 26.9.0 for exposure. Review saved queries using JSON data sources for absolute URLs pointing outside configured base URLs. Inspect network logs for outbound requests to unexpected external hosts from the Redash server.

Impact Analysis

An attacker with execute_query permission could exploit this to send requests to external hosts, potentially leaking HTTP Basic Auth credentials configured in the data source. This could lead to unauthorized access to external systems or data exfiltration. Private/internal address access is blocked if REDASH_ENFORCE_PRIVATE_IP_BLOCK is enabled.

Compliance Impact

This vulnerability could lead to unauthorized data exfiltration or access to external systems, potentially violating GDPR's data protection principles or HIPAA's safeguards for protected health information if credentials or sensitive data are exposed through SSRF attacks.

Mitigation Strategies

Upgrade to Redash version 26.9.0 or later. Remove HTTP Basic Auth credentials from vulnerable JSON data sources. Restrict execute_query permissions to trusted users. Enable REDASH_ENFORCE_PRIVATE_IP_BLOCK if not already set. Review and update saved queries to use relative URLs only.

Hi! I’m here to help you understand CVE-2026-76083. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70