# CVE-2023-0669: Fortra GoAnywhere MFT Remote Code Execution

> Pre-authentication attackers can execute arbitrary commands via deserialization in the License Response Servlet of Fortra GoAnywhere MFT.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 10 Feb 2023 (CISA KEV), used in ransomware
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2023
- **Updated:** 6 Aug 2026

## What is CVE-2023-0669?

CVE-2023-0669 is a high-severity unsafe deserialization vulnerability in Fortra Goanywhere MFT, published on 6 Feb 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Fortra (formerly, HelpSystems) GoAnywhere MFT suffers from a pre-authentication command injection vulnerability in the License Response Servlet due to deserializing an arbitrary attacker-controlled object. This issue was patched in version 7.1.2.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2023-0669?

It affects 1 product.


Products: Fortra Goanywhere Managed File Transfer.

## How do I fix CVE-2023-0669?

No fix has been published for CVE-2023-0669 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 Mar 2023.

## Is CVE-2023-0669 being exploited?

Yes. Attackers have exploited CVE-2023-0669 in the wild since at least 10 Feb 2023, including in ransomware campaigns.

Public exploit code:

- CVE-2023-0669 GoAnywhere MFT suffers from a pre-authentication command injection vulnerability in the License Response Servlet due to deserializing an arbitrary attacker-controlled object. (github_poc): https://github.com/0xf4n9x/CVE-2023-0669
- GoAnywhere MFT CVE-2023-0669 LicenseResponseServlet Deserialization Vulnerabilities Python RCE PoC(Proof of Concept) (github_poc): https://github.com/Avento/CVE-2023-0669
- CVE analysis for CVE-2023-0669 (github_poc): https://github.com/yosef0x01/CVE-2023-0669-Analysis
- Fortra GoAnywhere MFT Unsafe Deserialization RCE (metasploit)
- CVE-2023-0669 GoAnywhere MFT command injection vulnerability (github_poc): https://github.com/cataliniovita/CVE-2023-0669
- Goanywhere Encryption helper 7.1.1 - Remote Code Execution (RCE) (exploitdb)

## Other vulnerabilities in Fortra Goanywhere MFT

- [CVE-2025-10035](https://insights.sbomify.com/CVE-2025-10035/): Fortra GoAnywhere MFT Deserialization of Untrusted Data (critical 10.0, 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-2023-0669 and fix it if it is affected.

What it is: CVE-2023-0669 is a high-severity unsafe deserialization vulnerability in Fortra Goanywhere MFT, published on 6 Feb 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-0669 in the wild since at least 10 Feb 2023, 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-2023-0669/ (Markdown: https://insights.sbomify.com/CVE-2023-0669/index.md)
```

## Sources

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

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