CVE-2025-10932: Progress MOVEit Transfer · Uncontrolled Resource Consumption
Affects Progress MOVEit TransferSource CVE Database V5
Not known to be exploited · CVSS 8.2 High.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavencom.progress/moveit-transferpkg:maven/com.progress/moveit-transferOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should take the following specific steps to mitigate CVE-2025-10932: 1) Immediately inventory all MOVEit Transfer installations and identify affected versions. 2) Monitor Progress Software’s official channels for patch releases and apply updates to MOVEit Transfer versions 2023.1.16, 2024.1.7, or 2025.0.3 or later as soon as they become available. 3) Implement network-level protections such as rate limiting and anomaly detection on AS2 traffic to identify and block unusual request patterns that could indicate resource exhaustion attempts. 4) Configure system resource quotas and limits on servers hosting MOVEit Transfer to prevent a single process from consuming excessive CPU or memory. 5) Conduct regular performance and availability monitoring to detect early signs of resource consumption attacks. 6) Review and tighten firewall rules to restrict AS2 traffic to trusted partners and IP addresses. 7) Educate IT and security teams about the vulnerability and response procedures to ensure rapid incident handling. 8) Consider deploying web application firewalls (WAFs) with custom rules to mitigate malformed or suspicious AS2 requests. These targeted actions go beyond generic advice by focusing on the specific nature of the AS2 module and resource consumption vectors.
Description
Uncontrolled Resource Consumption vulnerability in Progress MOVEit Transfer (AS2 module).This issue affects MOVEit Transfer: from 2025.0.0 before 2025.0.3, from 2024.1.0 before 2024.1.7, from 2023.1.0 before 2023.1.16.