# CVE-2025-10932: AS2 module allows uncontrolled file uploads

> Attackers can cause uncontrolled resource consumption in the AS2 module, leading to denial of service.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Oct 2025
- **Updated:** 29 Oct 2025
- **Also known as:** GHSA-jcfc-r24f-p75w

## What is CVE-2025-10932?

CVE-2025-10932 is a high-severity denial of service vulnerability in Progress MOVEit Transfer, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

No fix has been published for CVE-2025-10932 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-10932 being exploited?

There is no known exploitation of CVE-2025-10932 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10932 is a high-severity denial of service vulnerability in Progress MOVEit Transfer, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10932 in the wild and no public exploit code.

Affected product: Progress MOVEit Transfer. 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-10932/ (Markdown: https://insights.sbomify.com/CVE-2025-10932/index.md)
```

## Sources

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

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