MOVEit Transfer: Improper Handling of Unicode Encoding
CVE-2026-89074 is a high-severity improper handling of unicode encoding vulnerability in MOVEit Transfer from Progress Software, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 2025.1.6, 2026.0.4 as the first without the flaw, so updating MOVEit Transfer to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.48% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update MOVEit Transfer to 2025.1.6 or 2026.0.4, whichever matches your release line, or a later version.
- Read the advisory on community.progress.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Progress Software | MOVEit Transfer | before 2025.1.6; 2026.0.0 up to, but not including, 2026.0.4 | 2025.1.6, 2026.0.4 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (progress.com) |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
Improper handling of unicode encoding vulnerability in Progress MOVEit Transfer. This issue affects MOVEit Transfer: before 2025.1.6 and from 2026.0.0 before 2026.0.4.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Handling of Unicode Encoding
The product does not properly handle when an input contains Unicode encoding.
How developers prevent this class of flaw
- Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
- Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
More Improper Handling of Unicode Encoding vulnerabilities (CWE-176)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in MOVEit Transfer
- 8.8 High severity
- 8.8 High severity
- 7.3 High severity
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
Recent Improper Handling of Unicode Encoding vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
- 7.2 High severity
- 7.3 High severity
Android Framework Privilege Escalation Exploited
- 9.8 Critical severity
Spotted an error? Tell us.