CVE-2021-41192

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 79.6%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 8%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Redash is a package for data visualization and sharing. If an admin sets up Redash versions 10.0.0 and prior without explicitly specifying the REDASH_COOKIE_SECRET or REDASH_SECRET_KEY environment variables, a default value is used for both that is the same across all installations. In such cases, the instance is vulnerable to attackers being able to forge sessions using the known default value. This issue only affects installations where the REDASH_COOKIE_SECRET or REDASH_SECRET_KEY environment variables have not been explicitly set. This issue does not affect users of the official Redash cloud images, Redash's Digital Ocean marketplace droplets, or the scripts in the getredash/setup repository. These instances automatically generate unique secret keys during installation. One can verify whether one's instance is affected by checking the value of the REDASH_COOKIE_SECRET environment variable. If it is c292a0a3aa32397cdb050e233733900f, should follow the steps to secure the instance, outlined in the GitHub Security Advisory.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
94.2%
KEV
Not listed

Published

November 24, 2021

Last Modified

November 21, 2024

References (6)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:06 UTCEPSS rescore
  2. 2026-07-21 15:22 UTCEPSS rescore
  3. 2026-07-21 15:22 UTCEPSS rescore
  4. 2026-07-20 17:05 UTCEPSS rescore
  5. 2026-07-19 14:29 UTCEPSS rescore
  6. 2026-07-19 02:27 UTCEPSS rescore
  7. 2026-07-18 10:02 UTCEPSS rescore
  8. 2026-07-18 10:02 UTCEPSS rescore
  9. 2026-07-18 06:59 UTCOSV refresh
  10. 2026-07-16 17:00 UTCEPSS rescore
  11. 2026-07-16 17:00 UTCEPSS rescore
  12. 2026-07-15 16:55 UTCEPSS rescore
  13. 2026-07-15 16:55 UTCEPSS rescore
  14. 2026-07-15 01:58 UTCEPSS rescore
  15. 2026-07-13 22:27 UTCEPSS rescore
  16. 2026-07-13 22:27 UTCEPSS rescore
  17. 2026-07-13 06:11 UTCEPSS rescore
  18. 2026-07-13 06:11 UTCEPSS rescore
  19. 2026-07-12 05:44 UTCEPSS rescore
  20. 2026-07-11 08:25 UTCEPSS rescore
  21. 2026-07-11 08:25 UTCEPSS rescore
  22. 2026-07-09 19:07 UTCEPSS rescore
  23. 2026-07-08 15:12 UTCEPSS rescore
  24. 2026-07-07 13:43 UTCEPSS rescore
  25. 2026-07-06 16:25 UTCEPSS rescore
Show 70 more
  1. 2026-07-06 16:25 UTCEPSS rescore
  2. 2026-07-06 02:21 UTCEPSS rescore
  3. 2026-07-06 02:21 UTCEPSS rescore
  4. 2026-07-05 02:28 UTCEPSS rescore
  5. 2026-07-05 02:28 UTCEPSS rescore
  6. 2026-07-04 06:29 UTCEPSS rescore
  7. 2026-07-04 06:29 UTCEPSS rescore
  8. 2026-07-02 16:57 UTCEPSS rescore
  9. 2026-07-01 15:04 UTCEPSS rescore
  10. 2026-06-30 23:20 UTCEPSS rescore
  11. 2026-06-30 23:20 UTCEPSS rescore
  12. 2026-06-30 04:30 UTCOSV refresh
  13. 2026-06-29 14:04 UTCEPSS rescore
  14. 2026-06-28 14:05 UTCEPSS rescore
  15. 2026-06-28 04:54 UTCEPSS rescore
  16. 2026-06-28 04:54 UTCEPSS rescore
  17. 2026-06-27 03:06 UTCEPSS rescore
  18. 2026-06-27 03:06 UTCEPSS rescore
  19. 2026-06-25 13:48 UTCEPSS rescore
  20. 2026-06-25 13:48 UTCEPSS rescore
  21. 2026-06-24 14:03 UTCEPSS rescore
  22. 2026-06-24 14:03 UTCEPSS rescore
  23. 2026-06-23 21:31 UTCEPSS rescore
  24. 2026-06-23 21:31 UTCEPSS rescore
  25. 2026-06-22 14:24 UTCEPSS rescore
  26. 2026-06-21 14:55 UTCEPSS rescore
  27. 2026-06-21 01:58 UTCEPSS rescore
  28. 2026-06-21 01:58 UTCEPSS rescore
  29. 2026-06-19 19:24 UTCEPSS rescore
  30. 2026-06-19 19:24 UTCEPSS rescore
  31. 2026-06-18 17:51 UTCEPSS rescore
  32. 2026-06-18 17:51 UTCEPSS rescore
  33. 2026-06-17 17:51 UTCEPSS rescore
  34. 2026-06-17 17:51 UTCEPSS rescore
  35. 2026-06-17 17:51 UTCEPSS rescore
  36. 2026-06-16 17:51 UTCEPSS rescore
  37. 2026-06-16 17:51 UTCEPSS rescore
  38. 2026-06-15 17:46 UTCEPSS rescore
  39. 2026-06-13 22:58 UTCEPSS rescore
  40. 2026-06-13 22:58 UTCEPSS rescore
  41. 2026-06-12 23:10 UTCEPSS rescore
  42. 2026-06-12 16:10 UTCOSV refresh
  43. 2026-06-11 13:58 UTCEPSS rescore
  44. 2026-06-11 13:58 UTCEPSS rescore
  45. 2026-06-10 22:16 UTCEPSS rescore
  46. 2026-06-10 22:16 UTCEPSS rescore
  47. 2026-06-10 13:20 UTCEPSS rescore
  48. 2026-06-07 15:23 UTCEPSS rescore
  49. 2026-06-07 15:23 UTCEPSS rescore
  50. 2026-06-06 13:46 UTCEPSS rescore
  51. 2026-06-06 13:46 UTCEPSS rescore
  52. 2026-06-05 22:45 UTCEPSS rescore
  53. 2026-06-05 06:09 UTCEPSS rescore
  54. 2026-06-05 06:09 UTCEPSS rescore
  55. 2026-06-02 20:11 UTCEPSS rescore
  56. 2026-06-02 20:11 UTCEPSS rescore
  57. 2026-06-01 13:50 UTCEPSS rescore
  58. 2026-06-01 13:50 UTCEPSS rescore
  59. 2026-05-31 00:15 UTCEPSS rescore
  60. 2026-05-31 00:15 UTCEPSS rescore
  61. 2026-05-28 13:43 UTCEPSS rescore
  62. 2026-05-28 13:43 UTCEPSS rescore
  63. 2026-05-27 13:39 UTCEPSS rescore
  64. 2026-05-27 13:39 UTCEPSS rescore
  65. 2026-05-26 13:42 UTCEPSS rescore
  66. 2026-05-26 13:42 UTCEPSS rescore
  67. 2026-05-26 07:17 UTCEPSS rescore
  68. 2026-05-26 07:17 UTCEPSS rescore
  69. 2026-05-26 07:17 UTCEPSS rescore
  70. 2026-05-26 07:08 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2021/CVE-2021-41192.yaml
    First seen Jan 1, 2021

    Redash Setup Configuration - Default Secrets Disclosure

    Open source ↗

Frequently asked(5)

What is CVE-2021-41192?
CVE-2021-41192 is a high vulnerability published on November 24, 2021. Redash is a package for data visualization and sharing. If an admin sets up Redash versions 10.0.0 and prior without explicitly specifying the REDASHCOOKIESECRET or REDASHSECRETKEY environment variables, a default value is used for both that is the same across all installations. In such cases, the…
When was CVE-2021-41192 disclosed?
CVE-2021-41192 was first published in the National Vulnerability Database on November 24, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-41192 actively exploited?
CVE-2021-41192 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 94.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2021-41192?
CVE-2021-41192 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2021-41192?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-41192, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2021-41192

Explore →

Is Your Infrastructure Affected by CVE-2021-41192?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs