Vendor scorecard
CISA lists 4 Fortra vulnerabilities as exploited in the wild, 0 of them added in the last 12 months (down from 1 in the 12 months before). 2 (50%) are known to be used in ransomware campaigns. For entries added in the last two years, the median time from CVE publication to the KEV listing was 11 days. Most affected: GoAnywhere MFT (2), Cobalt Strike (2).
| Product | KEV entries |
|---|---|
| GoAnywhere MFT | 2 |
| Cobalt Strike | 2 |
| CVE | Vulnerability | Added |
|---|---|---|
| CVE-2025-10035 | Fortra GoAnywhere MFT Deserialization of Untrusted Data VulnerabilityRANSOMWAREGoAnywhere MFT | |
| CVE-2022-42948 | Fortra Cobalt Strike User Interface Remote Code Execution VulnerabilityCobalt Strike | |
| CVE-2022-39197 | Fortra Cobalt Strike Teamserver Cross-Site Scripting (XSS) VulnerabilityCobalt Strike | |
| CVE-2023-0669 | Fortra GoAnywhere MFT Remote Code Execution VulnerabilityRANSOMWAREGoAnywhere MFT |
Get an email when CISA adds the next Fortra CVE.
How to read this: CISA KEV lists vulnerabilities with reliable evidence of exploitation; a vendor with many entries is often one with a large, internet-facing install base, not necessarily worse engineering. "Publication → KEV" is the median number of days between the CVE's publication and its addition to KEV, for entries added in the last 24 months (1 entries); it is an upper bound on how long defenders had, since exploitation usually starts before the listing. Under NIS2 article 21(2)(d), supplier security is part of your risk management; this page is a starting point for that review. Compare vendors on the scorecard index.
We assess supplier security for NIS2 and DORA, from exploited-CVE history and patch response to contract clauses and evidence packs.
Get in touch →