Skip to content
major vulnerability· requires attention

Affects Commvault DataCube (enterprise backup infrastructure); RCE in backup components can disrupt operations and data integrity across many organizations.

Applications

CVE-2026-77091

8.5
High
EPSS 0.13%Patch availableSep 8, 2026

Path traversal in Commvault DataCube enabling remote code execution.

common questions

Is CVE-2026-77091 being exploited?

Not confirmed. CVE-2026-77091 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.

How severe is CVE-2026-77091?

CVE-2026-77091 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-77091?

Yes. A fix has been recorded for CVE-2026-77091. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-77091 affect?

CVE-2026-77091 affects Commvault DataCube, Content Extractor, Index Store. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-77091?

Apply vendor maintenance release to Content Extractor and Index Store immediately.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Commvault DataCubeContent ExtractorIndex Store
impact

Path traversal bypasses security enforcement allowing remote code execution, arbitrary file write and potential full system compromise.

action required

Immediate action required

affected versions
Commvault Commvault Cloud
  • affected>= 11.46.0 and <= 11.46.19
  • affected>= 11.44.0 and <= 11.44.19
  • affected>= 11.40.0 and <= 11.40.71
  • affected>= 11.36.0 and <= 11.36.122

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free