SupersetApplication · Apache
CVE-2026-23982
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn Improper Authorization vulnerability exists in Apache Superset that allows a low-privileged user to bypass data access controls. When creating a dataset, Superset enforces permission checks to prevent users from querying unauthorized data. However, an authenticated attacker with permissions to write datasets and read charts can bypass these checks by overwriting the SQL query of an existing dataset. This issue affects Apache Superset: before 6.0.0. Users are recommended to upgrade to version 6.0.0, which fixes the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Superset before 6.0.0 contains an improper authorization vulnerability where authenticated low-privileged users with dataset write and chart read permissions can bypass data access controls by overwriting the SQL query of an existing dataset, allowing unauthorized data access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
SupersetApplication
< 6.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Apache Superset versionRun `superset version` or check the version through the Superset UI at /health or through pip: `pip show apache-superset`Affected if Installed version is below 6.0.0 (e.g., 5.x.x, 4.x.x, etc.)
-
Identify users with dataset write permissionsIn Superset admin panel, review user roles and dataset permissions. Look for users assigned roles that include 'dataset write' or 'dataset write on <dataset>' permissionsAffected if Any low-privileged user account has dataset write permission configured
-
Verify chart read permissions exist alongside dataset writeReview the same user accounts from step 2 to confirm they also possess chart read permissions on one or more chartsAffected if Any user has both dataset write and chart read permissions assigned to them
-
Confirm existing datasets are presentNavigate to Datasets in Superset UI or query the datasets table in the metadata database to list available datasetsAffected if Datasets exist in the Superset instance that could be modified by the user with write permissions
User is affected if running Superset version below 6.0.0 AND any authenticated user possesses both dataset write and chart read permissions on existing datasets, allowing potential SQL query overwriting to bypass data access controls.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.0.0
Upgrade to Apache Superset version 6.0.0 or later to resolve the authorization bypass.
6.0.0
- 1. Review the Apache Superset upgrade documentation for your deployment method
- 2. Create a backup of your current Superset configuration and database
- 3. Stop the Superset service
- 4. Upgrade Superset to version 6.0.0 using your package manager or installation method (e.g., pip install apache-superset==6.0.0, Docker, or Helm)
- 5. Run database migrations if required (superset db upgrade)
- 6. Restart the Superset service
- 7. Verify the upgrade was successful and test that the authorization bypass is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Superset
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23982 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-23982 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data