dbcve.org
SupersetApplication · Apache

CVE-2024-26016

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-28
Fix available
A fix is available. Upgrade to 3.0.4 / 3.1.1 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A low privilege authenticated user could import an existing dashboard or chart that they do not have access to and then modify its metadata, thereby gaining ownership of the object. However, it's important to note that access to the analytical data of these charts and dashboards would still be subject to validation based on data access privileges. This issue affects Apache Superset: before 3.0.4, from 3.1.0 before 3.1.1.Users are recommended to upgrade to version 3.1.1, 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 confidence

This is an IDOR/privilege escalation vulnerability in Apache Superset's dashboard and chart import functionality. An authenticated low-privilege user can import existing dashboards or charts they do not have access to, then modify the object's metadata to gain ownership. The fix requires adding proper authorization checks in the import workflow to verify the user has access rights before allowing import and ownership changes.

MitigationUpgrade Apache Superset to version 3.1.1 or later. Apply the patch which adds authorization validation to prevent unauthorized users from importing and taking ownership of objects they don't have access to.

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
Affected:< 3.0.4>= 3.1.0, < 3.1.1

CVSS 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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Apache Superset version
    Query the Superset metadata database (e.g., SELECT version FROM ab_user WHERE username='admin') or check the version via the /api/v1/health endpoint if exposed, or inspect the installed package (pip show apache-superset or equivalent)
    Affected if Version is below 3.0.4, or between 3.1.0 and 3.1.1 (inclusive of 3.1.0, exclusive of 3.1.1)
  2. Verify import API endpoints are accessible
    Check if the REST API endpoints /api/v1/chart/import/ and /api/v1/dashboard/import/ are reachable (e.g., curl -k -u <user>:<pass> https://<host>/api/v1/chart/import/)
    Affected if The import endpoints respond with HTTP 200 or 400 (indicating they exist and accept requests) rather than 401/403
  3. Confirm low-privilege user can access import functionality
    Using a low-privilege authenticated user account (e.g., gamma role), attempt a GET request to the import endpoints or check the Superset access logs for successful import-related requests from non-admin users
    Affected if Low-privilege users can successfully reach and interact with the import endpoints without receiving 403 Forbidden responses

If the Superset version falls within the affected ranges (< 3.0.4 or >= 3.1.0 to < 3.1.1) AND the import API endpoints are accessible to low-privilege users, the environment is vulnerable to CVE-2024-26016.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.0.4 / 3.1.1 or later
Fixed in 3.0.43.1.1
Interim mitigation

Upgrade Apache Superset to version 3.1.1 or later. Apply the patch which adds authorization validation to prevent unauthorized users from importing and taking ownership of objects they don't have access to.

Recommended fix High confidence

3.1.1

  1. Upgrade Apache Superset to version 3.1.1 or later
  2. Verify the upgrade was successful by checking the Superset version in the UI or via command line
  3. Confirm that the import functionality now properly validates ownership before allowing modification of imported dashboards and charts

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Superset Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26016 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-26016 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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