dbcve.org
Moveit TransferApplication · Progress

CVE-2026-10699

HIGH · 7.5 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 2025.0.8 / 2025.1.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

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
Missing release of memory after effective lifetime vulnerability in Progress MOVEit Transfer (Custom Reports modules). This issue affects MOVEit Transfer: from 2025.0.0 before 2025.0.8, from 2025.1.0 before 2025.1.4, from 2026.0.0 before 2026.0.1.

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 · high confidence

Memory leak vulnerability in MOVEit Transfer's Custom Reports modules where memory is not properly released after its effective lifetime. An unauthenticated remote attacker could potentially exploit this to cause memory exhaustion leading to denial of service.

MitigationUpgrade MOVEit Transfer to version 2025.0.8, 2025.1.4, 2026.0.1 or later to patch the memory leak in Custom Reports modules.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Moveit TransferApplication
Affected:<= 2024.1.8>= 2025.0.0, < 2025.0.8>= 2025.1.0, < 2025.1.4= 2026.0.0

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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Confirm MOVEit Transfer product
    Verify the installed product is MOVEit Transfer (not MOVEit DMZ or other Progress products). Check installed programs or service name.
    Affected if Product is MOVEit Transfer and version falls within affected ranges (<=2024.1.8, 2025.0.0-2025.0.7, 2025.1.0-2025.1.3, or 2026.0.0)
  2. Identify installed version
    Check the MOVEit Transfer version through the admin interface (Help > About) or by inspecting the installed program files for version metadata.
    Affected if Installed version matches any of the vulnerable version ranges listed in the CVE.
  3. Verify Custom Reports module is in use
    Check if the Custom Reports feature is enabled or configured in MOVEit Transfer. Review admin settings or configuration files for custom report definitions.
    Affected if Custom Reports module is enabled or has custom report configurations present.
  4. Monitor for memory exhaustion symptoms
    Review system event logs, MOVEit Transfer application logs, and Windows Performance Monitor for signs of memory pressure, out-of-memory errors, or unusual memory growth tied to report generation processes.
    Affected if Memory exhaustion events occur during or after custom report operations, indicating potential exploitation.

Environment is affected if MOVEit Transfer version is within the vulnerable ranges AND the Custom Reports module is enabled, with memory issues manifesting in logs or system performance.

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
Upgrade available Upgrade to 2025.0.8 / 2025.1.4 or later
Fixed in 2025.0.82025.1.4
Interim mitigation

Upgrade MOVEit Transfer to version 2025.0.8, 2025.1.4, 2026.0.1 or later to patch the memory leak in Custom Reports modules.

Recommended fix Moderate confidence

2026.0.1 (or 2025.1.4+ or 2025.0.8+ depending on your branch)

  1. 1. Identify the current installed version of MOVEit Transfer by checking the application or configuration files
  2. 2. Navigate to the Progress Community website (community.progress.com) or official Progress download portal to obtain the fixed version
  3. 3. Download the appropriate fixed version: 2025.0.8 or later for the 2025.0.x branch, 2025.1.4 or later for the 2025.1.x branch, or 2026.0.1 or later for the 2026.0.x branch
  4. 4. Review the upgrade documentation and release notes for MOVEit Transfer
  5. 5. Perform a backup of the current MOVEit Transfer installation and configuration
  6. 6. Apply the upgrade following the vendor's documented upgrade procedure
  7. 7. Verify the upgrade was successful and the memory leak vulnerability is resolved
Caveat Review release notes for any breaking changes between your current version and the target fixed version before upgrading

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

Fix this in Moveit Transfer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10699 — 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-2026-10699 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