Quick answers
- Is CVE-2026-77095 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77095 being exploited in the wild.
- How severe is CVE-2026-77095?
- Informational severity, published 13 October 2026.
- Which products and versions are affected?
- Commvault 11.46.0 to 11.46.29; 11.44.0 to 11.44.24; 11.40.0 to 11.40.77; 11.36.0 to 11.36.126.
- Is there a fix for CVE-2026-77095?
- Yes: fixed in Commvault 11.46.30 and higher, 11.44.25 and higher, 11.40.78 and higher, 11.36.127 and higher. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77095 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-77095?
- Check whether you run Commvault at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Commvault 11.46.30 and higher, 11.44.25 and higher, 11.40.78 and higher, 11.36.127 and higher
Technical details
CvFWD contains a null pointer dereference triggered by specific conditions, resulting in service availability disruption. The vulnerability affects multiple version branches of Commvault across Linux and Windows platforms with no authentication or network interaction required to trigger the crash. A fix is available in patched maintenance releases for all affected version lines.
Affected products
- Commvault Commvault 11.46.0 to 11.46.29; 11.44.0 to 11.44.24; 11.40.0 to 11.40.77; 11.36.0 to 11.36.126
Timeline
- 2026-10-13: disclosed