# CVE-2025-34028: Commvault Command Center Path Traversal

> Unauthenticated attackers can upload malicious ZIP files to achieve remote code execution via path traversal in Commvault Command Center.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:L/SI:H/SA:H`)
- **Exploited in the wild:** Yes, since 2 May 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2025
- **Updated:** 29 Nov 2025
- **Also known as:** GHSA-6q9c-pjw5-5rjm

## What is CVE-2025-34028?

CVE-2025-34028 is a critical path traversal vulnerability in Commvault Command Center Innovation Release, published on 22 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Commvault Command Center Innovation Release allows an unauthenticated actor to upload ZIP files that represent install packages that, when expanded by the target server, are vulnerable to path traversal vulnerability that can result in Remote Code Execution via malicious JSP.

This issue affects Command Center Innovation Release: 11.38.0 to 11.38.20. The vulnerability is fixed in 11.38.20 with SP38-CU20-433 and SP38-CU20-436 and also fixed in 11.38.25 with SP38-CU25-434 and SP38-CU25-438.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-34028?

It affects 1 product.


Products: Commvault Commvault.

## How do I fix CVE-2025-34028?

No fix has been published for CVE-2025-34028 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 23 May 2025.

## Is CVE-2025-34028 being exploited?

Yes. Attackers have exploited CVE-2025-34028 in the wild since at least 2 May 2025.

Public exploit code:

- https://github.com/watchtowrlabs/watchTowr-vs-Commvault-PreAuth-RCE-CVE-2025-34028 (github_poc): https://github.com/watchtowrlabs/watchTowr-vs-Commvault-PreAuth-RCE-CVE-2025-34028
- Proof-of-Concept (PoC) for CVE-2025-34028, a Remote Code Execution vulnerability in Commvault Command Center. This Python script scans single or multiple targets, executes commands, and reports vulnerable hosts. (github_poc): https://github.com/Mattb709/CVE-2025-34028-PoC-Commvault-RCE
- Commvault Remote Code Execution (CVE-2025-34028) NSE (github_poc): https://github.com/becrevex/Commvault-CVE-2025-34028
- Commvault CVE-2025-34028 endpoint scanner using Nmap NSE. For ethical testing and configuration validation. (github_poc): https://github.com/tinkerlev/commvault-cve2025-34028-check
- Commvault - SSRF via /commandcenter/deployWebpackage.do (nuclei): http/cves/2025/CVE-2025-34028.yaml

## Other vulnerabilities in Commvault Command Center Innovation Release

- [CVE-2025-3928](https://insights.sbomify.com/CVE-2025-3928/): Commvault Web Server Unspecified (high 8.7, exploited in the wild)
- [CVE-2017-18044](https://insights.sbomify.com/CVE-2017-18044/): Command injection in n/a (critical 9.8)
- [CVE-2026-77089](https://insights.sbomify.com/CVE-2026-77089/): Command Center API Authentication Bypass (critical 9.3)
- [CVE-2026-13737](https://insights.sbomify.com/CVE-2026-13737/): Command Restriction Bypass (critical 9.2)
- [CVE-2026-13738](https://insights.sbomify.com/CVE-2026-13738/): Improper Authorization Validation (critical 9.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34028 and fix it if it is affected.

What it is: CVE-2025-34028 is a critical path traversal vulnerability in Commvault Command Center Innovation Release, published on 22 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-34028 in the wild since at least 2 May 2025.

Affected product: Commvault Command Center Innovation Release. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-34028/ (Markdown: https://insights.sbomify.com/CVE-2025-34028/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-34028
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-34028
- OSV: https://osv.dev/vulnerability/CVE-2025-34028

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-34028/
Summaries are generated and may contain mistakes; the official description above is the record.