dbcve.org
CommvaultApplication

CVE-2025-57790

HIGH · 8.8 CVSS v3.1 Published 2025-08-20
Fix available
A fix is available. Upgrade to 11.36.60 or later.
See remediation →
94/100
Remediation priority · Urgent
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 security vulnerability has been identified that allows remote attackers to perform unauthorized file system access through a path traversal issue. The vulnerability may lead to remote code execution.

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

This is a path traversal vulnerability that allows remote attackers to manipulate file paths using '..' or absolute path sequences to access files outside the intended web root directory. Successful exploitation can lead to unauthorized file system reads/writes and potentially remote code execution if attacker-controlled files can be executed.

MitigationImplement strict input validation and sanitization for all file path parameters, use allow-lists for permitted paths, normalize paths before access checks, and ensure web servers run with minimal file system privileges.

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
CommvaultApplication
Affected:< 11.36.60

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Commvault version
    Locate the installed Commvault version through the administration console, command line (cvversion or similar), or check the software inventory. This is typically visible in the product UI under About or in the installer logs.
    Affected if The installed version is below 11.36.60
  2. Verify web console accessibility
    Determine if the Commvault web console or any HTTP-based service is exposed and reachable on the network. This may be on port 80/443 or a custom port configured during installation.
    Affected if The web interface is accessible and the version is below 11.36.60
  3. Check for file operation features
    Identify if any file read, file download, backup, or restore functionality that handles user-supplied paths is enabled in the Commvault deployment. Look for features involving file path parameters in the web UI or API endpoints.
    Affected if File operation features that accept path parameters are enabled and the version is below 11.36.60
  4. Review access logs for path traversal patterns
    Examine Commvault web server logs, audit logs, or security event logs for requests containing sequences like '../', '..\', or absolute paths (e.g., '/etc/passwd', 'C:\Windows\'). Search for abnormal file access attempts.
    Affected if Log analysis reveals path traversal attempts targeting files outside the intended web root, and the version is below 11.36.60

A system is affected if it runs Commvault version below 11.36.60 and exposes any web-based file handling functionality accessible to remote users.

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

Implement strict input validation and sanitization for all file path parameters, use allow-lists for permitted paths, normalize paths before access checks, and ensure web servers run with minimal file system privileges.

Recommended fix High confidence

Commvault version 11.36.60 or later

  1. Identify the current Commvault installation version
  2. If the current version is below 11.36.60, plan an upgrade to version 11.36.60 or later
  3. Download the Commvault update package from the official documentation.commvault.com or your maintenance portal
  4. Test the upgrade in a non-production environment first
  5. Apply the upgrade to production systems following Commvault standard upgrade procedures
  6. Verify the upgrade was successful by confirming the version is now 11.36.60 or higher
  7. Validate that the path traversal vulnerability is no longer present
Caveat Review Commvault release notes for 11.36.60 for any configuration or compatibility changes before upgrading

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

Fix this in Commvault Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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