# CVE-2026-77371: Redash: DuckDB query runner allows arbitrary file read/write via unrestricted external access

> Attackers with query access can read or write arbitrary files via DuckDB, potentially stealing secrets to bypass authentication.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-cr68-3xxj-cg9f

## What is CVE-2026-77371?

CVE-2026-77371 is a critical path traversal vulnerability in getredash redash, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-77371?


## How do I fix CVE-2026-77371?

No fix has been published for CVE-2026-77371 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-77371 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77371 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77371 and fix it if it is affected.

What it is: CVE-2026-77371 is a critical path traversal vulnerability in getredash redash, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77371 exists.

Affected product: getredash redash. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77371/ (Markdown: https://insights.sbomify.com/CVE-2026-77371/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77371
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77371
- OSV: https://osv.dev/vulnerability/CVE-2026-77371

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77371/
Summaries are generated and may contain mistakes; the official description above is the record.