CVE-2021-41192 — AI Deep Analysis Summary

Q: Who is affected? (Versions/Components)

👥 **Affected**: **Redash** versions **10.0.0 and earlier**. 📦 **Component**: The session management mechanism relying on `REDASH_COOKIE_SECRET`/`REDASH_SECRET_KEY`.

Q: Is exploitation threshold high? (Auth/Config)

⚡ **Threshold**: **LOW**. 🔑 **Auth**: Requires **Low Privilege** (PR:L) to access the instance initially. ⚙️ **Config**: Exploits **misconfiguration** (missing env vars). No UI interaction needed (UI:N).

Q: Is there a public Exp? (PoC/Wild Exploitation)

🔓 **Public Exp?**: **YES**. 📜 **PoC**: Available via **Nuclei templates** (projectdiscovery) and GitHub advisories. 🌍 **Wild Exp**: High risk due to predictable default secrets.

Q: Is it fixed officially? (Patch/Mitigation)

✅ **Fixed?**: **YES**. 🔧 **Patch**: Official commit `ce60d20` addresses the issue. 📢 **Advisory**: GHSA-g8xr-f424-h2rv confirms the fix.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. ⚠️ **Priority**: Critical for any unpatched Redash instance. 📉 **Impact**: High Confidentiality/Integrity impact (C:H, I:H). Fix immediately to prevent session hijacking.

Updated May 08, 2026 CVSS 8.1 · High

This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis →

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: Redash <=10.0.0 uses **hardcoded default secrets** for session cookies.…

Read full answer (login)

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-1188** (Insecure Default Initialization of Resource).…

Read full answer (login)

Q3Who is affected? (Versions/Components)

👥 **Affected**: **Redash** versions **10.0.0 and earlier**. <br>📦 **Component**: The session management mechanism relying on `REDASH_COOKIE_SECRET`/`REDASH_SECRET_KEY`.

Q4What can hackers do? (Privileges/Data)

🕵️ **Attacker Actions**: <br>1. **Forge Sessions**: Create valid auth tokens using the default secret. <br>2. **Full Access**: Bypass login to view/edit dashboards, queries, and sensitive data. <br>3.…

Read full answer (login)

Q5Is exploitation threshold high? (Auth/Config)

⚡ **Threshold**: **LOW**. <br>🔑 **Auth**: Requires **Low Privilege** (PR:L) to access the instance initially. <br>⚙️ **Config**: Exploits **misconfiguration** (missing env vars). No UI interaction needed (UI:N).

Q6Is there a public Exp? (PoC/Wild Exploitation)

🔓 **Public Exp?**: **YES**. <br>📜 **PoC**: Available via **Nuclei templates** (projectdiscovery) and GitHub advisories. <br>🌍 **Wild Exp**: High risk due to predictable default secrets.

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: <br>1. Scan for **Nuclei template** `CVE-2021-41192.yaml`. <br>2. Verify if `REDASH_COOKIE_SECRET` is **customized** in environment variables. <br>3.…

Read full answer (login)

Q8Is it fixed officially? (Patch/Mitigation)

✅ **Fixed?**: **YES**. <br>🔧 **Patch**: Official commit `ce60d20` addresses the issue. <br>📢 **Advisory**: GHSA-g8xr-f424-h2rv confirms the fix.

Q9What if no patch? (Workaround)

🚧 **No Patch?**: <br>1. **Immediately set** `REDASH_COOKIE_SECRET` and `REDASH_SECRET_KEY` to **strong, random values**. <br>2. **Rotate** all existing sessions/tokens. <br>3.…

Read full answer (login)

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. <br>⚠️ **Priority**: Critical for any unpatched Redash instance. <br>📉 **Impact**: High Confidentiality/Integrity impact (C:H, I:H). Fix immediately to prevent session hijacking.

Continue exploring

Vulnerability detail Full AI analysis (login) getredash CWE-1188