SupersetApplication · Apache
CVE-2025-48912
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 · uneditedAn authenticated malicious actor using specially crafted requests could bypass row level security configuration by injecting SQL into 'sqlExpression' fields. This allowed the execution of sub-queries to evade parsing defenses ultimately granting unauthorized access to data. 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 confidenceApache Superset before 4.1.2 contains a SQL injection vulnerability in sqlExpression fields that allows authenticated users to bypass row-level security controls. Attackers can inject sub-queries that evade parsing defenses, enabling unauthorized access to data that should be restricted by row-level security policies.
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
< 4.1.2CVSS 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.
-
Determine installed Apache Superset versionRun 'pip show apache-superset' or check the package version in your deployment. In the Superset UI, go to Settings > About to view the version.Affected if The installed version is lower than 4.1.2 (e.g., 4.1.1, 4.1.0, 4.0.x, 3.x, or earlier)
-
Identify if row-level security is enabledIn Superset UI, navigate to Settings > Row Level Security or query the database for RLS policies in the 'row_level_security' or similar table if using backend storage.Affected if Row-level security policies exist and are enforced on any dataset
-
Locate sqlExpression configurationsReview your dataset configurations, virtual datasets, or custom SQL metrics. Query the metadata database for entries containing sqlExpression or look in saved datasets where custom SQL expressions are defined.Affected if Any dataset or query configuration uses sqlExpression fields that could accept user-controlled input
-
Check for custom SQL-based security filtersExamine any row-level security filters that use custom SQL WHERE clauses, particularly those that rely on user attributes or session context.Affected if RLS filters contain dynamic SQL expressions that could be manipulated
-
Audit user permissions and RLS policy assignmentsReview which users or roles are assigned to row-level security policies, especially in datasets with sqlExpression-based filters.Affected if Authenticated users with limited permissions have access to datasets protected by sqlExpression-based RLS policies
You are affected if running Apache Superset version below 4.1.2 AND row-level security policies with sqlExpression fields are in use on any dataset.
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 · scoped4.1.2
Upgrade Apache Superset to version 4.1.2 or later. After upgrading, audit existing row-level security policies and sqlExpression configurations to verify they are functioning as intended.
4.1.2
- 1. Back up the existing Superset database and configuration files before proceeding with the upgrade.
- 2. Upgrade Apache Superset to version 4.1.2 using the appropriate method for your deployment (e.g., pip install apache-superset==4.1.2, docker pull apache/superset:4.1.2, or your package manager).
- 3. Restart all Superset services to load the new version.
- 4. Verify the upgrade was successful by checking the Superset version in the UI or via command line.
- 5. Test that row-level security configurations with sqlExpression fields are functioning correctly and that the SQL injection vulnerability is mitigated.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Superset
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48912 — 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-48912 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