SupersetApplication · Apache
CVE-2025-55675
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 · uneditedApache Superset contains an improper access control vulnerability in its /explore endpoint. A missing authorization check allows an authenticated user to discover metadata about datasources they do not have permission to access. By iterating through the datasource_id in the URL, an attacker can enumerate and confirm the existence and names of protected datasources, leading to sensitive information disclosure. 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 confidenceApache Superset versions before 5.0.0 contain an improper access control vulnerability in the /explore endpoint where missing authorization checks allow authenticated users to access metadata about datasources they lack permission to view. By manipulating the datasource_id parameter in the URL, an attacker can enumerate protected datasource names and confirm their existence, leading to sensitive information disclosure.
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
< 5.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Superset versionRun the command 'pip show apache-superset' or check the version in your package manager to determine the exact version number currently deployedAffected if The installed version is any release before 5.0.0 (e.g., 4.1.0, 4.0.1, 3.1.0, etc.)
-
Verify /explore endpoint access controlsLog in as a standard authenticated user with limited permissions, then attempt to access /explore/?datasource_id=<id> using datasource IDs from other users or protected datasourcesAffected if The endpoint returns datasource metadata (such as datasource names, table names, or schema information) for datasources the user has not been granted explicit access to
-
Check for datasource permission configurationsReview Superset security configuration at Security > List Roles and verify which roles are assigned permission to 'explore' or 'datasource_access' on specific databases/tablesAffected if The default Guest or Public roles have been granted access to the explore endpoint without proper datasource-level restrictions, or no datasource-specific access controls exist
You are affected if running any Apache Superset version below 5.0.0 AND the /explore endpoint is accessible to authenticated users who have not been explicitly granted datasource-level permissions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.0.0
Upgrade Apache Superset to version 5.0.0 or later to resolve the missing authorization check in the /explore endpoint.
5.0.0
- 1. Back up the current Superset installation and database before upgrading
- 2. Stop the Superset service
- 3. Upgrade Superset to version 5.0.0 using the package manager (e.g., pip install apache-superset==5.0.0 or the appropriate method for your installation)
- 4. Run any required database migrations (e.g., superset db upgrade)
- 5. Restart the Superset service
- 6. Verify the upgrade was successful and test that the /explore endpoint now properly enforces authorization checks
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Superset
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55675 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-55675 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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