Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Evidence dossier
CVE-2023-27524
Apache Superset: Session validation vulnerability when using provided default SECRET_KEY
gen-56ccdaf9Normalized restatement
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.
- State
- PUBLISHED
- Published
- Apr 24, 2023
- Updated
- Oct 21, 2025
- Evidence coverage
- 72%
2026-07-18 · v2026.06.15 · percentile 99.9%
Distinct CVSS assessments remain side by side; none are averaged.
Source comparison
Who said what
Apache Superset: Session validation vulnerability when using provided default SECRET_KEY
Apache Superset Insecure Default Initialization of Resource Vulnerability
Probability 0.974050000000; percentile 0.998900000000
Applicability
Cited product scope
[{"status": "affected", "version": "0", "versionType": "semver", "lessThanOrEqual": "2.0.1"}]unknowncpe:2.3:a:apache:superset:*:*:*:*:*:*:*:*; end including 2.0.1supportedAssessments
CVSS by origin
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:LCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:LLimitations and unknowns
- KEV membership is authoritative for the catalog, not proof of exposure in any environment.
- EPSS is a dated model probability and not an individual-environment prediction.
- Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
- NVD-carried upstream facts remain derivative and are not independent corroboration.
- Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
- NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
- Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
- Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.