CVE-2025-10035
Fortra GoAnywhere MFT Deserialization of Untrusted Data Vulnerability
Fortra GoAnywhere MFT
A deserialization vulnerability in the License Servlet of Fortra's GoAnywhere MFT allows an actor with a validly forged license response signature to deserialize an arbitrary actor-controlled object, possibly leading to command injection.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 29 September 2025. US federal agencies were required to remediate it by 20 October 2025. CISA records this vulnerability as known to be used in ransomware campaigns.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 99.8%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Frequently asked questions
Is CVE-2025-10035 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2025-10035.
What does CVE-2025-10035 affect?
CVE-2025-10035 affects Fortra GoAnywhere MFT. A deserialization vulnerability in the License Servlet of Fortra's GoAnywhere MFT allows an actor with a validly forged license response signature to deserialize an arbitrary actor-controlled object, possibly leading to command injection.
How severe is CVE-2025-10035?
CVE-2025-10035 is rated CRITICAL with a CVSS base score of 10. EPSS puts the probability of exploitation in the next 30 days at 99.8%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 20 October 2025.
How should organisations respond to CVE-2025-10035?
Apply the vendor patch for Fortra GoAnywhere MFT as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.