CVE-2025-34028 — Commvault Command Center Path Traversal Vulnerability
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (nuclei, github)+10
- EPSS 97.6% (30-day exploitation probability)+15
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
CISA required action CISA
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
US federal deadline: May 23, 2025 — passed 510 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Commvault Command Center Innovation Release, Commvault Commvault).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Commvault | Command Center Innovation Release | ≥ 11.38.0 and ≤ 11.38.25 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Commvault | Commvault | ≥ 11.38.0 and < 11.38.20 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.3 | CVSS 4.0 | Critical | — | — | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 9.3 | CVSS 4.0 | Critical | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
| 10.0 | CVSS 3.1 | Critical | 3.9 | 6.0 | nvd@nist.gov via NIST National Vulnerability Database |
| 10.0 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- watchtowrlabs/watchTowr-vs-Commvault-PreAuth-RCE-CVE-2025-34028 ★ 21 Apr 17, 2025
- 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. ★ 2 May 6, 2025
- Commvault Remote Code Execution (CVE-2025-34028) NSE ★ 1 May 6, 2025
- Commvault CVE-2025-34028 endpoint scanner using Nmap NSE. For ethical testing and configuration validation. ★ 0 Apr 24, 2025
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 97.60%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor file creation in web directories and paths with traversal sequences (../).
- Hunt retroactively in logs from before May 2, 2025 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · commvault/commvault
- CVSS changed · 9.3 → 10.0
- Source status changed · Published → Analyzed
- Record published
- Affected products added · commvault/command center innovation release
- CVSS changed · 9.3
- Source status changed · → Published
- SSVC assessment updated
- Added to CISA KEV (detected)
- Record created in this database
- 2025
- Added to CISA KEV catalog
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 3× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- documentation.commvault.com/securityadvisories/CV_2025_04_1.html
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- nvd.nist.gov/vuln/detail/CVE-2025-34028
- labs.watchtowr.com/fire-in-the-hole-were-breaching-the-vault-commvault-remote-code-execu
- github.com/advisories/GHSA-6q9c-pjw5-5rjm
- www.vulncheck.com/advisories/commvault-command-center-innovation-release-unauthenticate
- labs.watchtowr.com/fire-in-the-hole-were-breaching-the-vault-commvault-remote-code-execu
- github.com/watchtowrlabs/watchTowr-vs-Commvault-PreAuth-RCE-CVE-2025-34028
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-13739 Server-Side Request Forgery (SSRF) in Commvault Aug 11, 2026
- Critical CVE-2026-13737 Incorrect Authorization in Commvault Aug 11, 2026
- Critical CVE-2026-13738 Incorrect Authorization in Commvault Aug 11, 2026
- Medium CVE-2025-12776 Stored Cross-Site Scripting Jan 7, 2026
- High CVE-2025-3928 Commvault Web Server Unspecified Vulnerability KEV Apr 25, 2025
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-34028 is "Commvault Command Center Path Traversal Vulnerability", rated Critical. It affects Command Center Innovation Release (Commvault); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 10.0 describes technical severity. EPSS 97.60% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.