CriticalCVE-2025-34028

    Commvault Command Center Path Traversal Vulnerability (CVE-2025-34028)

    Published In CISA KEV since Sources: pwn.watch, SingCERT, CVE.org

    What is affected, what to do

    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 being actively exploited; treat it as a priority. Update commvault to version 11.38.20. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Commvault Command Center Innovation Release lte 11.38.0..11.38.25

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    10.0

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    10.0

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: pwn.watch, SingCERT, CVE.org

    97.6 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.90

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    238.54 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    10.0 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    10.0
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.3
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    97.6 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.90
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 2 May 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-22, CWE-306

    Response and mitigation

    Why act now?

    Prioritisation rationale

    Unauthenticated network reach, trivial attack complexity and direct RCE on a backup-management plane is why CISA added this CVE to KEV — compromising the Command Center hands the attacker the keys to the entire backup fabric, including restore targets, stored credentials and potentially production data. Exploitation likelihood ranks among the highest in the whole CVE corpus and public PoC code circulates. For NIS2-scoped organisations the host qualifies as an essential component (backup falls under business continuity): internet-exposed instances P1/emergency change, internally reachable instances P2 patched inside the next change window. CISA does not flag known ransomware use for this CVE, yet backup infrastructure is a generic primary target for ransomware operators and should be treated as pre-ransomware risk.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Patch Commvault Command Center Innovation Release immediately: upgrade to 11.38.20 with hotfix SP38-CU20-433 or SP38-CU20-436, or to 11.38.25 with SP38-CU25-434 or SP38-CU25-438. Any build from 11.38.0 up to unpatched 11.38.20 is vulnerable.
      • Until patched, remove the Command Center web UI (typically TCP/443, internally sometimes TCP/80 or ports in the 8400 range) from the public internet — restrict to VPN or jump-host access. The flaw is network-reachable and requires no authentication.
      • Emergency scoping: inventory every CommServe and WebServer role (install path Program Files\Commvault, processes cvd.exe, tomcat*), confirm build version via qlist media or the Admin Console, and compare against the fix matrix.
      • Inspect Tomcat webapp directories and upload/temp paths (e.g. \WebConsole\, \CVAppliance\, staging folders under \iDataAgent\) for unknown .jsp files, recently expanded ZIP archives and unusual timestamps since early 2025 — preserve forensically before patching overwrites artefacts.
      • Rotate Command Center service accounts (local service users and AD accounts running Commvault services) plus API/Qlogin credentials if compromise is suspected. Validate backup catalogue integrity, since RCE on the backup fabric has immediate supply-chain impact.
    2. Runbook step 2

      Mitigation layers

      • Network segmentation: place Command Center in a dedicated management VLAN with an explicit allowlist (admin jump hosts, monitoring). Block outbound internet traffic from the Commvault host at the firewall to defeat reverse shells and tool staging.
      • Front the Command Center with a WAF/reverse proxy; only permit multipart/form-data uploads to /commandcenter/, /webconsole/ upload endpoints from authenticated sessions. Drop requests containing path traversal sequences (..\, ..%2f, %2e%2e) or ZIP content types on these endpoints.
      • IPS rule: alert on inbound HTTP(S) requests carrying ZIP magic (PK\x03\x04) in the body to Commvault URIs. Starting-point Suricata/Snort signature: http.request_body; content:"PK|03 04|"; http.uri; content:"commandcenter";.
      • Endpoint hardening: do not run the Command Center Tomcat process as SYSTEM/root where vendor-supported; add an AppLocker/WDAC rule denying JSP execution outside the pristine webapp paths; minimise write permissions on the webroot to the installer service account only.
      • IAM: enforce MFA on all Commvault admin accounts, integrate SAML/SSO, disable local fallback accounts. Short-lived API tokens; separate roles for backup operations versus infrastructure administration.
      • Tomcat configuration monitoring: enable file integrity monitoring on the webapp directory with alerts on any new or modified .jsp, .war, .class file.
    3. Runbook step 3

      Detection rules

      • Tomcat localhost_access_log: POST requests with Content-Type application/zip or multipart/form-data to Command Center upload endpoints, followed within seconds by GET requests to previously unseen .jsp paths — the canonical dropper pattern.
      • Sysmon EID 1 (Process Create) on Commvault hosts: children of tomcat*.exe or java.exe spawning cmd.exe, powershell.exe, whoami, net user, cscript. KQL sketch: DeviceProcessEvents | where InitiatingProcessFileName in~ ("java.exe","tomcat9.exe") and FileName in~ ("cmd.exe","powershell.exe","rundll32.exe").
      • Sysmon EID 11 / Linux auditd path: file writes with .jsp extension outside the legitimate webapp directory, especially paths containing .. prior to normalisation or located in temp/staging folders.
      • Network telemetry (Zeek http.log, files.log): uploads with MIME application/zip to Commvault URIs sourced from non-administrative subnets; filter Zeek files.log on PK magic plus the Command Center host as destination.
      • Sigma shape: detection: selection: ParentImage|endswith: '\tomcat*.exe' Image|endswith: ('\cmd.exe','\powershell.exe','\sh','\bash') condition: selection — a backup server should never spawn interactive shells.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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.

    Source: pwn.watch, CSA/SingCERT, NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    CommvaultCommand Center Innovation Release
    • 11.38.0 – ≤ 11.38.25
    • —
    commvaultcommvault
    • 11.38.0 – < 11.38.20
    • 11.38.20

    Vendors and products

    Weakness classes (CWE)

    • CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

      Base

      The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

      Entry at MITRE CWE-22
    • CWE-306Missing Authentication for Critical Function

      Base

      The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

      Entry at MITRE CWE-306

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    GitHubwatchtowrlabs/watchTowr-vs-Commvault-PreAuth-RCE-CVE-2025-34028 (opens in a new tab)github.comPoC (publicly reported)reported, not verified—
    Reference tagged as exploitlabs.watchtowr.com (opens in a new tab)PoC (publicly reported)reported, not verified—

    References & sources

    • documentation.commvault.comCommvault advisory: Commvault Command CenterVendor advisory, Vendor advisory, pwn-watch
    • labs.watchtowr.comfire-in-the-hole-were-breaching-the-vault-commvault-remote-code…Exploit, Third-party advisory
    • github.comwatchtowrlabs/watchTowr-vs-Commvault-PreAuth-RCE-CVE-2025-34028Exploit, Exploit
    • vulncheck.comadvisories/commvault-command-center-innovation-release-unauthen…Third-party advisory, Third-party advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2025-34028government-resource, US government resource
    • pwn.watchpwn.watch: Commvault Command Center: Command Center Path Traversal Vulnerabilitypwn-watch
    • NVD (NIST)NVD: CVE-2025-34028pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2025-34028
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-34028"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-34028.svg?lang=en" alt="CVE-2025-34028 – NEOSEC Intel" height="20"></a>