getredash redash Improper Access Control Flaw (CVE-2026-77371) Rated CVSS 9.3
A newly published critical vulnerability in getredash redash carries a CVSS score of 9.3. Here is what is affected and how to respond.
Key points
- CVE-2026-77371 affects getredash redash.
- CVSS 9.3 (Critical).
- No exploitation confirmed yet.
getredash redash is affected by CVE-2026-77371, a improper access control that the National Vulnerability Database rates 9.3 out of 10.
At a glance
- CVE
- CVE-2026-77371
- Product
- getredash redash
- CVSS
- 9.3 Critical
- Weakness
- improper access control
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: 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.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Getredash | redash | >= 26.0.0, < 26.9.0 |
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-77371
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-77371?
CVE-2026-77371 is a improper access control vulnerability in getredash redash.
How severe is CVE-2026-77371?
It has a CVSS score of 9.3 Critical.
Is CVE-2026-77371 being exploited?
There is no public confirmation of exploitation at the time of publication.
