External risk intelligence

Redash DuckDB Query Runner Allows File Access and Disclosure

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-77371

Redash is typically deployed as a web-based data visualization and dashboard platform, which is often configured as an internet-facing or externally reachable application to allow for collaborative data sharing and remote access by users, making the platform's features, including data source query runners, commonly accessible via the web interface.

Authentication Bypass

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in the DuckDB query runner for Redash could allow a user with query access to retrieve or write files using the Redash process's privileges. This could potentially expose sensitive application secrets, leading to forged sessions and authentication bypass.

  • Allows unauthorized file access or modification.
  • Critical for protecting sensitive application secrets.
  • Confirm relevance and assess potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by leveraging a user who already has query access to a DuckDB data source within Redash. This access allows the attacker to use built-in file-reading or writing functions of DuckDB, potentially leading to the disclosure of sensitive application secrets or unauthorized file modifications with the privileges of the Redash process.

  • Requires query access to a DuckDB data source.
  • Attacker uses native DuckDB file functions.
  • Risk of reading secrets or writing files.

Live Threat

Current exploitation, exposure, and threat context

A user with query access to an administrator-created DuckDB data source could leverage native file-reading functions to access files readable by the Redash process. This could also allow writing files with the process's privileges, potentially exposing sensitive application secrets like API keys or session tokens.

  • Application files and secrets.
  • Query access to read/write files.
  • Forged sessions and authentication bypass.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Redash application owner, likely a data or platform team, is responsible for addressing this vulnerability. The first step is to identify all Redash instances, confirm their accessibility and criticality, and locate the specific asset owner. Subsequently, a remediation plan should be developed based on the assessed risk.

  • Data platform team owns the issue.
  • Verify Redash instance accessibility and criticality.
  • Plan remediation based on exposure and risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Redash?

Redash is a software platform designed for data visualization, dashboarding, and collaborative sharing. It allows teams to connect to various databases, run queries, and turn that data into charts or reports. By centralizing data access, it enables organizations to create live dashboards for decision-making.

What does CVE-2026-77371 mean for Redash?

This CVE represents an Improper Access Control weakness (CWE-284). In affected versions, the DuckDB query runner allows connections with external access enabled by default. This permits a user who already has query-level permissions to bypass intended restrictions and use built-in functions to read or write files directly on the underlying server.

How can an attacker trigger this vulnerability?

An attacker needs existing query access to a DuckDB data source that an administrator has already configured in Redash. If a user lacks this specific query access, they cannot initiate the malicious commands. The issue does not stem from external network requests but rather from misuse of authorized query capabilities.

Do I need to worry if my Redash instance is internal?

Yes, you should evaluate the risk regardless of network placement. According to Halo Surface Signal, Redash is often deployed as a web-based dashboard platform intended for collaborative sharing, which frequently results in it being reachable via the web. Even if kept internal, any user with query access represents a potential entry point.

How do I respond to the Redash security advisory?

First, identify all Redash instances running in your environment and determine who manages them. Once you have a list of deployments, prioritize updating them to version 26.9.0, which resolves the DuckDB configuration issue. Assess whether any existing DuckDB data sources were used by unauthorized parties while the vulnerability was present.

References