dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2025-10932

HIGH · 8.2 CVSS v3.1 Published 2025-10-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An Uncontrolled Resource Consumption vulnerability exists in the AS2 (Applicability Statement 2) module of Progress MOVEit Transfer. The AS2 module, used for EDI (Electronic Data Interchange) communications, fails to properly limit or restrict resource consumption, allowing an attacker to potentially exhaust server resources (CPU, memory, disk, or network connections) leading to denial of service. This affects specific versions of MOVEit Transfer across three major release lines.

MitigationApply the vendor-provided patches: upgrade to MOVEit Transfer 2025.0.3, 2024.1.7, or 2023.1.16 or later to remediate the uncontrolled resource consumption in the AS2 module.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify MOVEit Transfer is installed
    Check the installed version by reviewing the MOVEit Transfer application info, typically found in the program files or via the admin interface at /moveitadmin. The version is displayed on the login page or in the system information section.
    Affected if MOVEit Transfer is installed and running.
  2. Determine the exact version number
    In the MOVEit Transfer admin interface, navigate to Help > About or check the version displayed in the application header. Alternatively, check the installed software list on the server for 'Progress MOVEit Transfer' with its version number.
    Affected if The installed version falls within these vulnerable ranges: 2025.0.0 through 2025.0.2, 2024.0.0 through 2024.1.6, or 2023.0.0 through 2023.1.15.
  3. Confirm AS2 module is enabled
    In the MOVEit Transfer admin interface, navigate to System Settings > Modules or check the AS2 configuration page at /as2/config. The AS2 module must be active for this vulnerability to be exploitable.
    Affected if The AS2 module is enabled and configured for receiving AS2 transmissions.
  4. Review AS2 connection and transfer settings
    Check AS2 incoming connection limits and transfer size thresholds in the AS2 module configuration. Look for settings controlling concurrent connections, memory allocation per transfer, or disk usage for incoming files.
    Affected if Default or permissive AS2 settings are in place without rate limiting or resource caps configured.

A user is affected if MOVEit Transfer version is 2023.x before 1.16, 2024.x before 1.7, or 2025.x before 0.3 AND the AS2 module is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided patches: upgrade to MOVEit Transfer 2025.0.3, 2024.1.7, or 2023.1.16 or later to remediate the uncontrolled resource consumption in the AS2 module.

Recommended fix High confidence

MOVEit Transfer 2025.0.3 or later; 2024.1.7 or later; 2023.1.16 or later

  1. Identify your current MOVEit Transfer version from the admin interface or system information
  2. Review the upgrade path for your current version and select an upgrade path: for 2025.x versions upgrade to 2025.0.3 or later; for 2024.x versions upgrade to 2024.1.7 or later; for 2023.x versions upgrade to 2023.1.16 or later
  3. Backup your current MOVEit Transfer configuration and database before proceeding with the upgrade
  4. Download the appropriate upgrade package from Progress Customer Portal or authorized distribution channels
  5. Follow Progress MOVEit Transfer upgrade documentation to apply the upgrade, ensuring the AS2 module is included in the update
  6. After upgrade, verify the AS2 module is running the patched version and confirm the vulnerability is resolved
  7. Monitor system resources to confirm the uncontrolled resource consumption issue is remediated
Caveat Review Progress release notes for any breaking changes between your current version and target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10932 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10932 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data