Vendor evidence profile

Cohesity: what the public record shows

nexalign keeps a continuously updated evidence record on Cohesity for backup and recovery decisions: 16 items from 3 kinds of source, covering July 2019 to July 2026. Every item on this page links to the source it came from, carrying the date that source states and saying so plainly where it states none.

In one line

This record holds 5 advisories attributed to Cohesity products across 16 evidence items in total, none of them in the CISA catalogue of known exploited vulnerabilities. 100 percent of the record comes from sources Cohesity cannot edit. Whether Cohesity suits your decision is not on this page: that depends on your criteria, your compliance scope and your shortlist, and this record does not know them.

Evidence items

16

in this record

Attributed advisories

5

none known exploited

Authoritative share

94%

government registers

Last checked

Jul 28, 2026

sources re-queried

How independent is this record

Sources are not equal. A vendor can rewrite its own website overnight and optimise it for whatever a language model is likely to quote. It cannot edit a government vulnerability register or a years-old discussion thread. Every item in this record is classified by how much the vendor could influence it, and the score below is the weighted result.

Independence of this record

Objectivity score 98/100

Authoritative
15 items, 94 percent
Independent
1 items, 6 percent
Vendor-controlled
0 items, 0 percent

100 percent of this record comes from sources Cohesity does not control. The remainder is Cohesity's own material and is marked as such wherever it appears.

Where this record comes from

These are the sources that contributed to the Cohesity record, with the body that operates each one. No rating, score or ranking is taken from anywhere, and no vendor pays to appear in this index or to change what it says.

SourceOperated byClassificationItemsLatest
European Vulnerability DatabaseENISA, European UnionAuthoritative10Mar 03, 2026
National Vulnerability DatabaseNIST, United States Department of CommerceAuthoritative5Mar 03, 2026
Analyst, review and reference sourcesRecognised analysts, review marketplaces and technology pressIndependent1Jul 14, 2026

Documented vulnerabilities

Vulnerability registers are searched by keyword, so an advisory about a different product often mentions Cohesity in passing. An entry is only listed here when a structural signal ties it to a product of Cohesity: an advisory reference on the vendor's own domain, Cohesity as the assigning authority, or the affected product list naming it. 5 records passed that test.

  • CVE-2025-67840highCVSS 7.2Mar 03, 2026

    Multiple authenticated OS command injection vulnerabilities exist in the Cohesity (formerly Stone Ram) TranZman 4.0 Build 14614 through TZM_1757588060_SEP2025_FULL.depot web application API…

  • CVE-2025-63912highCVSS 7.5Mar 03, 2026

    Cohesity TranZman Migration Appliance Release 4.0 Build 14614 was discovered to use a weak cryptography algorithm for data encryption, allowing attackers to trivially reverse the encyption…

  • CVE-2025-63911highCVSS 7.2Mar 03, 2026

    Cohesity TranZman Migration Appliance Release 4.0 Build 14614 was discovered to contain an authenticated command injection vulnerability.

  • CVE-2025-63910highCVSS 7.2Mar 03, 2026

    An authenticated arbitrary file upload vulnerability in Cohesity TranZman Migration Appliance Release 4.0 Build 14614 allows attackers with Administrator privileges to execute arbitrary…

  • CVE-2025-63909highCVSS 7.2Mar 03, 2026

    Incorrect access control in the component /opt/SRLtzm/bin/TapeDumper of Cohesity TranZman Migration Appliance Release 4.0 Build 14614 allows attackers to escalate privileges to root and…

What practitioners report

Public threads in which engineers and administrators discuss running this product. Only threads naming Cohesity in their own title are listed, so a discussion about someone else's incident cannot end up under this vendor. Not curated for sentiment: 0 threads in the record, most recent first.

Nothing on record from this kind of source.

Independent coverage

Recognised analysts, review marketplaces and neutral technology press that name Cohesity. This section runs on a fixed list of such outlets rather than on whatever a web search returns for the company name, because that search is dominated by sales-intelligence profiles and directory listings which say nothing about the product. Social networks and press-release wires are excluded outright.

  • en.wikipedia.orgdate not recordedIndependent

    Cohesity - Wikipedia

    en.wikipedia.org

What Cohesity publishes about itself

The vendor's own documentation, kept separate from everything above and marked as vendor-controlled. It is useful, and it is a claim until an independent source confirms it.

Nothing on record from this kind of source.

What this record cannot tell you

A record is only trustworthy if it is explicit about its holes. These are the ones in the Cohesity record right now.

  • A further 5 register entries mention Cohesity without naming a product of Cohesity as affected. They are excluded rather than counted as vulnerabilities.

  • No public practitioner discussion naming Cohesity 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 Cohesity 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

Is Cohesity a safe choice?

The public record holds 5 advisories attributed to Cohesity products and 16 evidence items in total. None of them appears in the CISA catalogue of known exploited vulnerabilities. Whether that is acceptable depends on your risk appetite, your compliance scope and the alternatives on your shortlist, none of which a public page can know. This page reports the record; it does not rate the vendor.

Where does the Cohesity data on this page come from?

From 3 kinds of source: European Vulnerability Database, operated by ENISA, European Union; National Vulnerability Database, operated by NIST, United States Department of Commerce; Analyst, review and reference sources, operated by Recognised analysts, review marketplaces and technology press. Every item carries its source URL and, where the source states one, its date.

Does Cohesity pay to appear in this index?

No. There is no paid placement, no sponsored profile and no way for a vendor to change what the record says. Vendors are listed because their category comes up in enterprise technology decisions. Corrections to a specific entry can be sent to [email protected] and are checked against the source.

How much of the Cohesity record is the vendor's own material?

0 percent. The remaining 100 percent comes from sources Cohesity does not control. Vendor-published material stays in the record and is labelled as vendor-controlled rather than counted as independent confirmation.

Why does this page not say whether Cohesity is better than the alternatives?

Because better only exists relative to a decision. Which criteria matter, how heavily each one weighs and what counts as a dealbreaker are properties of the buyer, not of the vendor. DecisionOS takes this same evidence pool and scores it against the criteria of an actual decision, which is where a comparison becomes meaningful.

How this record is built

Sources are queried on a schedule, not on request. Findings are stored with the source URL, the event date and a content hash, so the same item is never counted twice and every statement stays traceable to where it came from.

Nothing on this page is written by a language model. Counts are counts, dates are the dates the sources carry, and titles are the sources' own wording. Where a section is empty, that is a finding in itself and is stated as one.

Corrections are welcome. If an entry is wrong or an attribution is off, write to [email protected] and it gets checked against the source.

Citing this page

nexalign GmbH, Cohesity: what the public record shows, nexalign vendor evidence index, Jul 28, 2026. Available at nexalign.io/vendors/cohesity.

The whole field is on one page: every backup and recovery vendor with a published record, with the size of each.

Turn this record into a decision you can defend

DecisionOS takes the same evidence pool this page is built from, weighs it against the criteria of your actual decision, and produces a memo that holds up in front of a board and an auditor.

Cohesity: vulnerabilities, sources and open questions | DecisionOS by nexalign