dbcve.org
SupersetApplication · Apache

CVE-2025-55674

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-14
Fix available
A fix is available. Upgrade to 5.0.0 or later.
See remediation →
71/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 bypass of the DISALLOWED_SQL_FUNCTIONS security feature in Apache Superset allows for the execution of blocked SQL functions. An attacker can use a special inline block to circumvent the denylist. This allows a user with SQL Lab access to execute functions that were intended to be disabled, leading to the disclosure of sensitive database information like the software version. This issue affects Apache Superset: before 5.0.0. Users are recommended to upgrade to version 5.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 confidence

Apache Superset contains a security feature bypass in its DISALLOWED_SQL_FUNCTIONS denylist mechanism. An attacker with SQL Lab access can use a specially crafted inline block to circumvent the function denylist and execute blocked SQL functions, enabling disclosure of sensitive database metadata such as software version information.

MitigationUpgrade to Apache Superset 5.0.0 or later, which contains the fix for this security feature 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:< 5.0.0

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
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 checks

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

  1. Identify Apache Superset installation
    Run command 'pip show apache-superset' or check your container/application metadata to retrieve the installed version of Apache Superset
    Affected if The installed version is below 5.0.0 (e.g., 4.1.0, 4.0.0, 3.x, etc.)
  2. Verify SQL Lab is enabled
    Check Superset configuration file (superset_config.py) for 'FEATURE_FLAGS' dictionary containing 'SQL_LAB_ENABLED': True, or inspect the web UI to confirm SQL Lab feature is accessible to users
    Affected if SQL Lab is enabled and accessible to untrusted users
  3. Check DISALLOWED_SQL_FUNCTIONS denylist configuration
    Inspect the Superset configuration file (superset_config.py) for the 'DISALLOWED_SQL_FUNCTIONS' setting, which should contain a list of blocked SQL function names as strings (e.g., ['version()', '@@version'])
    Affected if DISALLOWED_SQL_FUNCTIONS is configured with a non-empty list of functions to block
  4. Confirm SQL Lab access for untrusted users
    Review user roles and permissions in Superset admin panel, specifically checking which roles have access to 'can_sqllab' or SQL Lab functionality, including any database connections configured in SQL Lab
    Affected if Users with SQL Lab access can write and execute arbitrary SQL queries against databases

Your environment is affected if you run Apache Superset version below 5.0.0 with SQL Lab enabled and have configured DISALLOWED_SQL_FUNCTIONS to block certain SQL functions, as an attacker with SQL Lab access could bypass that denylist.

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

Upgrade to Apache Superset 5.0.0 or later, which contains the fix for this security feature bypass.

Recommended fix High confidence

5.0.0

  1. 1. Create a full backup of your current Superset installation including database and configuration
  2. 2. Review the official Apache Superset upgrade documentation for migrating to version 5.0.0
  3. 3. Upgrade Apache Superset to version 5.0.0 using your package manager or deployment method (e.g., pip install apache-superset==5.0.0 or Helm upgrade)
  4. 4. After upgrade, verify that the DISALLOWED_SQL_FUNCTIONS security feature properly blocks the previously bypassed SQL functions
  5. 5. Test that SQL Lab functionality works as expected with the new version
  6. 6. Monitor logs for any attempted exploitation of this vulnerability
Caveat Review 5.0.0 release notes for potential breaking changes in features, APIs, or database migrations before upgrading

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

Fix this in Superset Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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