# CVE-2025-10035: Fortra GoAnywhere MFT Deserialization of Untrusted Data

> An attacker with a forged license signature can trigger deserialization in GoAnywhere MFT, potentially leading to remote code execution.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 29 Sep 2025 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2025
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-fcfw-g3g2-2588

## What is CVE-2025-10035?

CVE-2025-10035 is a critical unsafe deserialization vulnerability in Fortra GoAnywhere MFT, published on 18 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2025-10035?

It affects 1 product.


Products: Fortra Goanywhere Managed File Transfer.

## How do I fix CVE-2025-10035?

No fix has been published for CVE-2025-10035 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 20 Oct 2025.

## Is CVE-2025-10035 being exploited?

Yes. Attackers have exploited CVE-2025-10035 in the wild since at least 29 Sep 2025, including in ransomware campaigns.

Public exploit code:

- Detection for CVE-2025-10035 (github_poc): https://github.com/rxerium/CVE-2025-10035
- 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. (github_poc): https://github.com/ThemeHackers/CVE-2025-10035
- CVE-2025-10035_GoAnywhere Get RCE (github_poc): https://github.com/orange0Mint/CVE-2025-10035_GoAnywhere
- CVE-2025-10035 Research writeup (github_poc): https://github.com/sentinel-aidefense/CVE-2025-10035
- CVE-2025-10035 is a critical vulnerability in Fortra GoAnywhere MFT that may allow attackers to execute commands remotely on a vulnerable server. (github_poc): https://github.com/dkchaiv/CVE-2025-10035
- GoAnywhere - Authentication Bypass (nuclei): http/cves/2025/CVE-2025-10035.yaml

## Other vulnerabilities in Fortra GoAnywhere MFT

- [CVE-2023-0669](https://insights.sbomify.com/CVE-2023-0669/): Fortra GoAnywhere MFT Remote Code Execution (high 7.2, exploited in the wild)
- [CVE-2024-0204](https://insights.sbomify.com/CVE-2024-0204/): Authentication Bypass in GoAnywhere MFT (critical 9.8)
- [CVE-2025-14362](https://insights.sbomify.com/CVE-2025-14362/): GoAnywhere MFT SFTP Service Login Vulnerable to Brute Force Attack Under Certain Circumstances (high 7.3)
- [CVE-2026-1089](https://insights.sbomify.com/CVE-2026-1089/): User‑Controlled HTTP Header In Fortra's GoAnywhere MFT Allows Arbitrary DNS Lookups (medium 6.5)
- [CVE-2024-25157](https://insights.sbomify.com/CVE-2024-25157/): Authentication bypass in GoAnywhere MFT prior to 7.6.0 (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10035 and fix it if it is affected.

What it is: CVE-2025-10035 is a critical unsafe deserialization vulnerability in Fortra GoAnywhere MFT, published on 18 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-10035 in the wild since at least 29 Sep 2025, including in ransomware campaigns.

Affected product: Fortra GoAnywhere MFT. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10035/ (Markdown: https://insights.sbomify.com/CVE-2025-10035/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10035
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10035
- OSV: https://osv.dev/vulnerability/CVE-2025-10035

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10035/
Summaries are generated and may contain mistakes; the official description above is the record.