dbcve.org
SupersetApplication · Apache

CVE-2025-27696

HIGH · 8.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 4.1.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Incorrect Authorization vulnerability in Apache Superset allows ownership takeover of dashboards, charts or datasets by authenticated users with read permissions. This issue affects Apache Superset: through 4.1.1. Users are recommended to upgrade to version 4.1.2 or above, 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

Apache Superset versions through 4.1.1 contain an incorrect authorization vulnerability where authenticated users with only read permissions can take ownership of dashboards, charts, or datasets they have access to. This represents a vertical privilege escalation where users can bypass intended ownership transfer restrictions.

MitigationUpgrade Apache Superset to version 4.1.2 or above to obtain the vendor patch that fixes this authorization bypass.

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:< 4.1.2

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 your Apache Superset version
    Check the installed Superset version by running 'superset version' or inspecting the package.json/metastore for the version field
    Affected if The installed version is any version prior to 4.1.2 (e.g., 4.1.1, 4.0.0, 3.x, 2.x)
  2. Review users with read-only dataset permissions
    Query the permission tables (e.g., security_manager.find_role) for roles assigned 'datasource_read' permission on datasets without 'datasource_write' or 'owner' permissions
    Affected if Any authenticated user账户拥有对数据集的只读权限而没有写入权限或所有权
  3. Review users with read-only chart permissions
    Query the permission tables for roles with 'chart_read' permission on charts without 'chart_write' or 'owner' permissions
    Affected if Any authenticated user账户拥有对图表的只读权限而没有写入权限或所有权
  4. Review users with read-only dashboard permissions
    Query the permission tables for roles with 'dashboard_read' permission on dashboards without 'dashboard_write' or 'owner' permissions
    Affected if Any authenticated user账户拥有对仪表板的只读权限而没有写入权限或所有权
  5. Audit recent ownership changes
    Review Superset audit logs or security logs for events where read-only users have modified ownership of dashboards, charts, or datasets
    Affected if Audit logs show ownership transfer or permission changes initiated by users who previously only had read access

You are affected if your Superset version is below 4.1.2 AND you have users with only read permissions on any dashboards, charts, or datasets.

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 4.1.2 or later
Fixed in 4.1.2
Interim mitigation

Upgrade Apache Superset to version 4.1.2 or above to obtain the vendor patch that fixes this authorization bypass.

Recommended fix High confidence

4.1.2

  1. 1. Back up your current Superset database and configuration files before upgrading.
  2. 2. Upgrade Apache Superset to version 4.1.2 or higher. For pip installations: pip install apache-superset>=4.1.2
  3. 3. For Docker-based deployments, update your image tag to use version 4.1.2 or later.
  4. 4. Run database migrations after upgrade: superset db upgrade
  5. 5. Restart the Superset services to apply the changes.
  6. 6. Verify that the upgrade was successful by logging in and confirming dashboard, chart, and dataset ownership controls work correctly.
Caveat Review release notes for any breaking changes between your current version and 4.1.2; major version upgrades may include configuration or feature changes

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27696 — 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-2025-27696 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