basicsecurity.net
Proof, not just disclosure.
Threats / Commvault / CVE-2025-34028
CVE-2025-34028 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Commvault Command Center vulnerability

Commvault Command Center contains a path traversal vulnerability (CWE-22) allowing remote unauthenticated attackers to execute arbitrary code. The vulnerability is actively exploited in the wild.

Verdict

Today item — known-exploited.

A critical remote code execution flaw in Commvault Command Center enables unauthenticated attackers to bypass file system restrictions through path traversal, leading to arbitrary code execution. Active exploitation in the wild indicates immediate risk to deployed instances.

CISA KEV Yes · 2025-05-023EPSS 0.97157 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
228 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-05-02).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.97157 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Commvault, Command Center. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-22 · Path TraversalPath traversal / file
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious request containing path traversal sequences to escape intended directory restrictions in the Command Center application.
Business
Attackers gain unauthorized file system access to sensitive backup infrastructure, compromising data protection controls.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I leverage the path traversal to write or modify executable files in locations where the application process has write permissions.
Business
Arbitrary code execution within the Command Center process context enables attackers to establish persistence and lateral movement within backup environments.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute commands with the privileges of the Command Center service account to exfiltrate backup data or encrypt it for extortion.
Business
Backup systems become compromised, enabling data theft, destruction, or ransom scenarios that undermine business continuity and data recovery capabilities.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 228 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by VulnCheck (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2
    Catalogued by VulnCheckCNA
    Credited with finding itSonny of watchTowrfinder