dbcve.org
SupersetApplication · Apache

CVE-2026-23983

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-24
Fix available
A fix is available. Upgrade to 6.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 Sensitive Data Exposure vulnerability exists in Apache Superset allowing authenticated users to retrieve sensitive user information. The Tag endpoint (disabled by default) allows users to retrieve a list of objects associated with a specific tag. When these associated objects include Users, the API response improperly serializes and returns sensitive fields, including password hashes (pbkdf2), email addresses, and login statistics. This vulnerability allows authenticated users with low privileges (e.g., Gamma role) to view sensitive authentication data This issue affects Apache Superset: before 6.0.0. Users are recommended to upgrade to version 6.0.0, which fixes the issue or make sure TAGGING_SYSTEM is False (Apache Superset current default)

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

The Tag endpoint API in Apache Superset improperly serializes User objects when returning associated objects for a tag. This exposes sensitive fields including pbkdf2 password hashes, email addresses, and login statistics to any authenticated user, even those with minimal Gamma-level privileges.

MitigationUpgrade Apache Superset to version 6.0.0 or disable the tagging system by setting TAGGING_SYSTEM to False in the configuration.

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:< 6.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. Check installed Apache Superset version
    Run the command: superset version or inspect the installed package version via pip show apache-superset or grep the version in your package manager
    Affected if The installed version is prior to 6.0.0 (e.g., 5.x.x, 4.x.x, etc.)
  2. Verify TAGGING_SYSTEM configuration setting
    Inspect the Superset configuration file (superset_config.py) or check the environment variable TAGGING_SYSTEM. Look for the setting: TAGGING_SYSTEM = True or confirm it is unset (defaults to enabled)
    Affected if TAGGING_SYSTEM is set to True or is not explicitly set to False in the configuration
  3. Confirm Tag API endpoint is accessible
    As an authenticated user with Gamma-level privileges, attempt a GET request to the tag endpoint (e.g., /api/v1/tag/ or /api/v1/tag/<tag_id>/associated) or check API documentation for the tag endpoint
    Affected if The API responds successfully and returns data containing user objects with sensitive fields
  4. Check if tags exist in the system
    Query the database for existing tags (table: tags) or use the Superset UI to list defined tags if you have any access
    Affected if Any tags are defined and associated with User objects, which could be returned through the vulnerable API serialization

You are affected if you run Apache Superset version below 6.0.0 with TAGGING_SYSTEM enabled (not set to False) and have tags defined that could expose serialized user data through the API.

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

Upgrade Apache Superset to version 6.0.0 or disable the tagging system by setting TAGGING_SYSTEM to False in the configuration.

Recommended fix High confidence

6.0.0

  1. Upgrade Apache Superset to version 6.0.0 or later to receive the security patch
  2. After upgrading, verify that the Tag endpoint no longer returns sensitive user fields in API responses
  3. Alternatively, if upgrading is not immediately possible, ensure TAGGING_SYSTEM is set to False in the Superset configuration (this is the default setting)
  4. Review user role assignments to ensure only necessary privileges are granted

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

Fix this in Superset Scoped from the published advisory
  • Consultation1.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,220
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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