dbcve.org
SupersetApplication · Apache

CVE-2026-23969

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-24
Fix available
A fix is available. Upgrade to 4.1.2 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
Apache Superset utilizes a configurable dictionary, DISALLOWED_SQL_FUNCTIONS, to restrict the execution of potentially sensitive SQL functions within SQL Lab and charts. While this feature included restrictions for engines like PostgreSQL, a vulnerability was reported where the default list for the ClickHouse engine was incomplete. This issue affects Apache Superset: before 4.1.2. Users are recommended to upgrade to version 4.1.2, 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's DISALLOWED_SQL_FUNCTIONS configuration feature, which blocks potentially dangerous SQL functions in SQL Lab and chart executions, had an incomplete default restriction list for the ClickHouse database engine. This allowed certain sensitive SQL functions to execute that should have been blocked.

MitigationUpgrade to Apache Superset 4.1.2 or manually add the missing ClickHouse SQL functions to the DISALLOWED_SQL_FUNCTIONS configuration blocklist.

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
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 installed Apache Superset version
    Check the Superset version number in your installation (typically via superset --version, package manager, or the superset_config.py file)
    Affected if The installed version is lower than 4.1.2 (e.g., 4.1.1, 4.0.0, 3.x, etc.)
  2. Confirm ClickHouse database engine is connected
    Review your configured database connections in Superset and identify any entries using the ClickHouse database engine type
    Affected if At least one ClickHouse database is connected to Superset and accessible via SQL Lab
  3. Locate DISALLOWED_SQL_FUNCTIONS configuration
    Inspect your superset_config.py or environment configuration for the DISALLOWED_SQL_FUNCTIONS setting
    Affected if The configuration exists and defines function restrictions for ClickHouse (or uses the default list without custom overrides)
  4. Verify function blocklist coverage for ClickHouse
    Compare the DISALLOWED_SQL_FUNCTIONS entries for the ClickHouse engine against known sensitive functions that should be blocked (e.g., functions related to file operations, system access, or sensitive data retrieval)
    Affected if The blocklist is empty, missing, or does not include the sensitive functions that should be restricted for ClickHouse

You are affected if your Superset version is below 4.1.2 AND you have a ClickHouse database connected with the default DISALLOWED_SQL_FUNCTIONS configuration that lacks complete function restrictions for ClickHouse.

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 to Apache Superset 4.1.2 or manually add the missing ClickHouse SQL functions to the DISALLOWED_SQL_FUNCTIONS configuration blocklist.

Recommended fix High confidence

4.1.2

  1. 1. Backup your existing Superset database and configuration before upgrading.
  2. 2. Stop the Superset service to prevent data inconsistency during upgrade.
  3. 3. Upgrade Apache Superset to version 4.1.2 using your installation method (e.g., pip install apache-superset==4.1.2, Docker, or package manager).
  4. 4. Run any database migrations required for the new version (typically: superset db upgrade).
  5. 5. Restart the Superset service.
  6. 6. Verify the DISALLOWED_SQL_FUNCTIONS configuration now includes the complete ClickHouse restrictions.
Caveat Review release notes for 4.1.2 for any breaking changes or deprecations before upgrading

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

Fix this in Superset Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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