dbcve.org
Data LakehouseApplication · Dell

CVE-2025-46608

HIGH · 7.2 CVSS v3.1 Published 2025-11-12
Fix available
A fix is available. Upgrade to 1.6.0.0 or later.
See remediation →
78/100
Remediation priority · High
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
Dell Data Lakehouse, versions prior to 1.6.0.0, contain(s) an Improper Access Control vulnerability. A high privileged attacker with remote access could potentially exploit this vulnerability, leading to Elevation of privileges. This vulnerability is considered Critical, as it may result in unauthorized access with elevated privileges, compromising system integrity and customer data. Dell recommends customers upgrade to the latest version at the earliest opportunity.

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 · moderate confidence

Dell Data Lakehouse versions before 1.6.0.0 contain an Improper Access Control vulnerability that allows a high-privileged attacker with remote access to elevate privileges beyond their assigned permissions, potentially compromising system integrity and customer data.

MitigationUpgrade Dell Data Lakehouse to version 1.6.0.0 or later to address the improper access control vulnerability.

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
Data LakehouseApplication
Affected:< 1.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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 if Dell Data Lakehouse is present
    Locate Dell Data Lakehouse installation in your environment using your software inventory or deployment records
    Affected if Dell Data Lakehouse is not found in your inventory, this CVE does not apply
  2. Determine installed version
    Check the installed version of Dell Data Lakehouse using the product's version command, configuration file, or administrative console
    Affected if Unable to determine version - treat as potentially affected if product is present
  3. Compare version against affected range
    Compare your installed version to the vulnerable range: any version before 1.6.0.0 is affected
    Affected if Installed version is below 1.6.0.0 (for example 1.5.x, 1.4.x, or earlier)
  4. Assess remote access exposure
    Determine if the Dell Data Lakehouse instance is accessible remotely over network connections
    Affected if System is exposed to remote network access and version is below 1.6.0.0 - this combination enables the attack vector described

Your environment is affected if Dell Data Lakehouse version is below 1.6.0.0 and the system accepts remote connections, allowing a high-privileged attacker to exploit the improper access control for privilege escalation.

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

Upgrade Dell Data Lakehouse to version 1.6.0.0 or later to address the improper access control vulnerability.

Recommended fix High confidence

1.6.0.0

  1. Review the upgrade documentation for Dell Data Lakehouse on support.dell.com
  2. Download Dell Data Lakehouse version 1.6.0.0 or later from the Dell support portal
  3. Schedule a maintenance window for the upgrade process
  4. Back up all existing data and configurations
  5. Execute the upgrade following the documented upgrade procedure
  6. Verify the upgrade was successful and the new version is running
  7. Confirm the vulnerability is remediated

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

Fix this in Data Lakehouse Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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