CVE-2026-77371
9.3CriticalPublished 14 Oct 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-284
Impact
Authenticated users with query permissions on a DuckDB data source can read and write arbitrary files accessible to the Redash process. They can extract application secrets like REDASH_SECRET_KEY to forge sessions and achieve full authentication bypass.
Root cause
The DuckDB query runner initializes connections with enable_external_access left at its default value of true, allowing arbitrary filesystem read and write operations.
Affected systems
Redash 26.0.0 through versions prior to 26.9.0
CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Fix & remediation
Upgrade Redash to version 26.9.0 or later. If updating immediately is not possible, disable or remove all DuckDB data sources and revoke user permissions to query them.
$ pip install --upgrade 'redash>=26.9.0'AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
Redash is a package for data visualization and sharing. From 26.0.0 until 26.9.0, the DuckDB query runner's _connect() path in redash/query_runner/duckdb.py created connections with enable_external_access left at its default value of true. A user with query access to an administrator-created DuckDB data source could use native file-reading functions to retrieve files readable by the Redash process or use COPY TO to write files with that process's privileges. Reading application secrets such as REDASH_COOKIE_SECRET or REDASH_SECRET_KEY could also enable forged sessions and authentication bypass. This issue is fixed in version 26.9.0.