Evidence comparison

Commvault and Veritas NetBackup: what the public record shows about each

Both products turn up on backup and recovery shortlists, so this page puts their two evidence records next to each other: 38 items on Commvault and 56 on Veritas NetBackup, each one linked to the source it came from. It does not name a winner, and the section below explains why the numbers cannot be subtracted from one another.

Read the counts correctly

More advisories does not mean less secure. A vulnerability register records what researchers found and what the vendor disclosed. A product deployed in thousands of organisations with a mature disclosure process accumulates far more entries than a product nobody audits. A low count can mean a small install base, a young product or a vendor that publishes little, and a high count often marks the opposite.

The two counts are not measured with equal precision. An advisory is only listed against a vendor when the register ties it to one of its products by name, and vendors differ enormously in how consistently their products are named. Here that gap is 17 unattributable entries for Commvault against 25 for Veritas NetBackup, which moves the advisory row far more than the products do. Both numbers are in the table so the difference is visible rather than hidden.

Treat this page as two records shown together, never as one score minus another.

The two records side by side

MeasureCommvaultVeritas NetBackup
Evidence items in the recordSize of the record, not a quality signal.3856
Kinds of source63
Advisories attributed to the vendor's productsCounts scrutiny and deployment breadth. See the caution above.1121
Register entries that could not be attributedEntries naming the vendor that could not be tied to one of its products, so they are excluded from the row above. Read the two rows together: where this number is high, the registers describe that vendor's products less consistently, and the advisory count above says more about naming than about the product.1725
Of those, in the CISA known-exploited catalogueExploitation observed in the wild. The one count worth reading closely.20
Share from government registers87%82%
Share the vendor cannot edit100%100%
Public practitioner threadsReflects community size as much as product behaviour.00
Most recent entryJul 17, 2026Jul 17, 2026
Sources last re-queriedJul 17, 2026Jul 17, 2026

Where each record comes from

The registers and platforms behind each column, with the body that operates each one. A record resting on government registers carries different weight from one resting on the vendor's own documentation, which is why this is shown per vendor rather than merged.

Commvault

SourceOperated byClassificationItemsLatest
European Vulnerability DatabaseENISA, European UnionAuthoritative20Jun 10, 2026
CERT-Bund security advisoriesBSI, Federal Republic of GermanyAuthoritative7Jun 11, 2026
National Vulnerability DatabaseNIST, United States Department of CommerceAuthoritative4Jun 10, 2026
Known Exploited Vulnerabilities catalogueCISA, United StatesAuthoritative2May 02, 2025
Analyst, review and reference sourcesRecognised analysts, review marketplaces and technology pressIndependent4Jul 17, 2026
Engineering discussionsHacker News, public threadsIndependent1Jul 16, 2026

Veritas NetBackup

SourceOperated byClassificationItemsLatest
European Vulnerability DatabaseENISA, European UnionAuthoritative25Feb 01, 2026
CERT-Bund security advisoriesBSI, Federal Republic of GermanyAuthoritative21Dec 04, 2024
Analyst, review and reference sourcesRecognised analysts, review marketplaces and technology pressIndependent10Jul 17, 2026

Documented vulnerabilities

Only entries tied to a product of the named vendor by a structural signal are listed: an advisory reference on the vendor's own domain, the vendor as the assigning authority, or the affected product list naming it. Entries that merely mention a vendor in passing are excluded from both columns.

Commvault

  • CVE-2025-34028criticalCVSS 9.3Known exploitedMay 02, 2025

    Commvault Command Center Path Traversal Vulnerability

  • CVE-2025-3928criticalCVSS 8.7Known exploitedApr 28, 2025

    Commvault Web Server Unspecified Vulnerability

  • WID-SEC-2026-0563lowCVSS 4.2Mar 03, 2026

    Affected products: Commvault Backup & Recovery

  • CVE-2025-12776lowCVSS 1.8Jan 07, 2026

    The Report Builder component of the application stores user input directly in a web page and displays it to other users, which raised concerns about a possible Cross-Site Scripting (XSS)…

  • WID-SEC-2025-1867highCVSS 9.9Aug 21, 2025

    Affected products: Commvault Backup & Recovery

  • WID-SEC-2025-1652mediumCVSS 7.3Jul 28, 2025

    Affected products: Commvault Backup & Recovery

Veritas NetBackup

  • WID-SEC-2024-3600mediumCVSS 7.8Dec 04, 2024

    Affected products: Veritas NetBackup

  • WID-SEC-2024-3331mediumCVSS 7.3Nov 20, 2024

    Affected products: Veritas NetBackup

  • WID-SEC-2024-1001mediumCVSS 6.8May 03, 2024

    Affected products: Veritas NetBackup

  • WID-SEC-2024-0864mediumCVSS 7.1Apr 26, 2024

    Affected products: Veritas NetBackup

  • WID-SEC-2023-1801highCVSS 9.8Mar 07, 2024

    Affected products: Veritas NetBackup

  • WID-SEC-2023-2044highCVSS 9.8Aug 11, 2023

    Affected products: Veritas NetBackup

What practitioners report

Public threads naming each product in their own title. Not curated for sentiment, and not counted as a verdict: a loud thread is one team's experience, not a measurement.

Commvault

Nothing on record from this kind of source.

Veritas NetBackup

Nothing on record from this kind of source.

What neither record can tell you

The two lists below are the honest holes in each record. Everything a choice between these two actually turns on sits outside both of them.

Commvault

  • A further 17 register entries mention Commvault without naming a product of Commvault as affected. They are excluded rather than counted as vulnerabilities.
  • No public practitioner discussion naming Commvault was found in the indexed threads. Operational experience with this product is not represented in this record.
  • Pricing, contract terms, notice periods and support commitments are not part of any public register. They come from the vendor and belong in a negotiation record.
  • Certification status such as ISO 27001, SOC 2 or BSI C5 has to be checked against the current certificate and its stated scope. A valid certificate can still exclude the product being bought.

Veritas NetBackup

  • A further 25 register entries mention Veritas NetBackup without naming a product of Veritas NetBackup as affected. They are excluded rather than counted as vulnerabilities.
  • No public practitioner discussion naming Veritas NetBackup was found in the indexed threads. Operational experience with this product is not represented in this record.
  • Pricing, contract terms, notice periods and support commitments are not part of any public register. They come from the vendor and belong in a negotiation record.
  • Certification status such as ISO 27001, SOC 2 or BSI C5 has to be checked against the current certificate and its stated scope. A valid certificate can still exclude the product being bought.

Whether Commvault is the right choice is not on this page

A record of what is true about a vendor is one half of a decision. The other half is your context: which criteria matter, how heavily each one weighs, what is a hard no, and who has to sign the result off. No public page can know that, and any page that claims to rank vendors for you is guessing at it.

Typical criteria for this category

Needs your case
  • Data Sovereignty & Residencyweight
  • Certifications (BSI C5, ISO 27001, SOC 2)weight
  • Scalability & Performanceweight
  • Migration Complexityweight
  • Vendor Lock-in Riskweight

Criteria shown as examples for backup and recovery. Weighting and fit are properties of your decision, not of the vendor, so they are not published here.

What DecisionOS adds on top of this record

  • The vendor scored against your criteria with your weighting, not against a generic ranking
  • A dealbreaker check against your hard constraints: data residency, contract terms, existing stack
  • A side-by-side view of the alternatives on your shortlist, built from this same evidence pool
  • This evidence mapped onto your compliance scope: NIS2, DORA, ISO 27001, SOC 2
  • A decision memo your board can read, with the trade-offs and the reasoning on the record

Questions this page answers

Which is better, Commvault or Veritas NetBackup?

This page does not answer that, and no public page can. Better exists only relative to a decision: which criteria matter, how heavily each weighs, what counts as a dealbreaker and which systems the product has to live next to. What this page gives you is the evidence on both, 38 items on Commvault and 56 on Veritas NetBackup, each with its source, so the judgement rests on the record rather than on marketing.

Does Commvault or Veritas NetBackup have more vulnerabilities?

Veritas NetBackup currently has 21 attributed advisories in this record and Commvault has 11. That comparison is easy to misread. A vulnerability register records what researchers found and what the vendor disclosed, so a widely deployed product with an active disclosure process accumulates more entries than one nobody audits. A low count can equally mean a small install base or a vendor that publishes little. The two figures are also not measured with equal precision: an advisory only counts here when a register ties it to a named product, and 17 entries naming Commvault and 25 naming Veritas NetBackup could not be tied to one. The count worth reading closely is how many entries appear in the CISA catalogue of known exploited vulnerabilities, which is 2 for Commvault and 0 for Veritas NetBackup.

How independent is the evidence on Commvault and Veritas NetBackup?

100 percent of the Commvault record and 100 percent of the Veritas NetBackup record come from sources the vendor does not control: government vulnerability registers, public practitioner threads and a fixed list of recognised analysts and technology press. Material either vendor publishes about itself stays in the record and is labelled as a claim.

What does this comparison of Commvault and Veritas NetBackup leave out?

Pricing, contract terms, notice periods, support commitments and the current scope of any certificate. None of those appear in a public register; they come from the vendor and belong in a negotiation record. Fit with your existing stack and your compliance scope is also absent, because it is a property of your organisation rather than of a backup and recovery product.

Why does nexalign publish this instead of ranking Commvault and Veritas NetBackup?

Because a ranking would have to invent the buyer. Every quadrant and score sheet silently assumes a weighting that belongs to someone else's decision. nexalign publishes the record and keeps the weighting where it belongs, in DecisionOS, where it is set by the people who have to defend the outcome.

The full records

Two records do not make a decision

Choosing between Commvault and Veritas NetBackup depends on which criteria matter to you, how heavily each one weighs, what your hard constraints are and who has to sign the result off. DecisionOS takes this same evidence pool, scores it against the criteria of your actual decision and produces a memo that holds up in front of a board and an auditor.

Commvault vs Veritas NetBackup: the public evidence on both, side by side | DecisionOS by nexalign