CVE-2025-2298: Dremio Software Auth Bypass Vulnerability

CVE-2025-2298 Overview

CVE-2025-2298 is an improper authorization vulnerability in Dremio Software that allows authenticated users to delete arbitrary files accessible to the system. The flaw exists on an API endpoint that fails to enforce access controls on file paths supplied by callers. Any authenticated user can target system files and remote storage backends, including Amazon S3, Azure Blob Storage, and local filesystems. Successful exploitation results in data loss, denial of service, and potential escalation depending on the files removed. The issue is tracked under CWE-862: Missing Authorization.

Critical Impact
Any authenticated Dremio user can delete arbitrary files across local and remote storage, leading to data loss, denial of service, and downstream system compromise.

Affected Products

Dremio versions below 24.0.0
Dremio 24.3.0 through 24.3.16, 25.0.0 through 25.0.14, and 25.1.0 through 25.1.7
Dremio 25.2.0 through 25.2.4

Discovery Timeline

2025-04-21 - CVE-2025-2298 published to NVD
2026-04-15 - Last updated in NVD database

Technical Details for CVE-2025-2298

Vulnerability Analysis

The vulnerability resides in a Dremio API endpoint that accepts a file path argument for deletion operations. The endpoint authenticates the caller but does not verify that the requested path falls within the caller's authorized scope. Because Dremio executes the deletion using the privileges of the underlying service account, the target file does not need to belong to the requesting user. Files writable by the Dremio process across mounted filesystems and configured object stores become reachable.

The impact extends beyond user data. Catalog metadata, internal configuration files, log files, and dataset artifacts stored in S3 or Azure Blob Storage are all candidates for deletion. Removing required system files can render Dremio inoperable, while deleting datasets directly damages downstream analytics pipelines that rely on the storage backend.

Root Cause

The root cause is a missing authorization check on the file deletion API endpoint. The handler trusts the path supplied in the request without validating ownership, project scope, or path canonicalization against the user's permissions. This places the vulnerability in the CWE-862 class of access control failures.

Attack Vector

An attacker requires only network access to the Dremio API and valid low-privilege credentials. The attacker issues a crafted request to the vulnerable deletion endpoint and supplies an absolute or remote path. The server performs the delete operation using its own privileges, returning success regardless of the caller's intended scope. The vulnerability is described in the Dremio Bulletin April 2025 without proof-of-concept code.

Detection Methods for CVE-2025-2298

Indicators of Compromise

Unexpected deletion of files in S3 buckets, Azure Blob containers, or local volumes accessed by the Dremio service account.
Dremio server errors or startup failures caused by missing configuration, metadata, or catalog files.
API access logs showing deletion requests from low-privilege user sessions referencing paths outside their assigned projects.

Detection Strategies

Enable verbose audit logging on the Dremio API and alert on calls to file deletion endpoints originating from non-administrative accounts.
Correlate Dremio audit events with cloud storage delete events in AWS CloudTrail and Azure Storage diagnostic logs to identify deletions triggered by the Dremio service principal.
Baseline normal deletion volume per user and trigger anomalies when a single account initiates a burst of delete operations.

Monitoring Recommendations

Forward Dremio application logs and cloud storage data-plane logs to a centralized analytics platform for cross-source correlation.
Monitor object storage versioning and lifecycle metrics for unusual delete or version-purge activity tied to the Dremio identity.
Track Dremio process restarts and catalog integrity errors that may indicate prior file removal.

How to Mitigate CVE-2025-2298

Immediate Actions Required

Upgrade to a fixed Dremio release: 24.3.17, 25.0.15, 25.1.8, 25.2.5, or 26.0.0 or later.
Audit Dremio user accounts and revoke unnecessary access until patching is complete.
Enable object storage versioning and immutability where supported to permit recovery of deleted files.

Patch Information

Dremio published fixes in the Dremio Bulletin April 2025. The corrected releases are 24.3.17 and later, 25.0.15 and later, 25.1.8 and later, 25.2.5 and later, and the 26.0.0 line. Operators running any unsupported version below 24.0.0 should upgrade to a current supported release.

Workarounds

Restrict the Dremio service account's IAM permissions and filesystem ACLs to the minimum paths required for operation, limiting the blast radius of arbitrary deletes.
Place Dremio API access behind network controls that enforce strong authentication and limit which users can authenticate to the service.
Enable object lock or write-once-read-many (WORM) policies on critical S3 buckets and Azure containers used by Dremio.

bash

# Example: restrict S3 permissions for the Dremio service principal
# Replace s3:DeleteObject with a scoped policy that excludes critical prefixes
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Deny",
      "Action": ["s3:DeleteObject", "s3:DeleteObjectVersion"],
      "Resource": [
        "arn:aws:s3:::dremio-catalog/*",
        "arn:aws:s3:::dremio-config/*"
      ]
    }
  ]
}