CVE-2023-27524: Apache Superset · Insecure Default Initialization of Resource
Affects Apache SupersetSource CVE Database V5
Exploited in the wild · KEV due 29 Jan 2024 · public exploit available (Metasploit, Exploit-DB) · 98% EPSS : apply the vendor's fix or mitigations to Apache Superset now.
Data as of 26 Oct 2026, 06:26 UTC
- KEV deadline
- US federal agencies must patch by this date; a sensible deadline for everyone else.
- EPSS
- 98.1% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:LExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 24 Apr 2023
Detectable: evidence found.
Weaponised: evidence found.
2 Metasploit modules · 1 Exploit-DB entry, 29 days after disclosure
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 259 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by apache
, 53 days before disclosure
CVE published
on cve.org
, t = 0
First Exploit-DB entry (opens in a new tab)
Apache Superset 2.0.0 - Authentication Bypass
, 29 days after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
, 259 days after disclosure
KEV remediation due
US federal deadline
, 280 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIapache-supersetpkg:pypi/apache-supersetOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
Session Validation attacks in Apache Superset versions up to and including 2.0.1. Installations that have not altered the default configured SECRET_KEY according to installation instructions allow for an attacker to authenticate and access unauthorized resources. This does not affect Superset administrators who have changed the default value for SECRET_KEY config. All superset installations should always set a unique secure random SECRET_KEY. Your SECRET_KEY is used to securely sign all session cookies and encrypting sensitive information on the database. Add a strong SECRET_KEY to your `superset_config.py` file like: SECRET_KEY = <YOUR_OWN_RANDOM_GENERATED_SECRET_KEY> Alternatively you can set it with `SUPERSET_SECRET_KEY` environment variable.
References
- lists.apache.org/thread/n0ftx60sllf527j7g11kmt24wvof8xyk (opens in a new tab)
- openwall.com/lists/oss-security/2023/04/24/2 (opens in a new tab)
- packetstormsecurity.com/files/172522/Apache-Superset-2.0.0-Authentication-Bypass.html (opens in a new tab)
- packetstormsecurity.com/files/175094/Apache-Superset-2.0.0-Remote-Code-Execution.html (opens in a new tab)
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-27524 (opens in a new tab)