Is CVE-2026-10699 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-10699 being exploited in the wild.

How severe is CVE-2026-10699?

High severity, with a CVSS score of 7.5, published 8 July 2026.

Which products and versions are affected?

Progress MOVEit Transfer 2025.0.0 before 2025.0.8, 2025.1.0 before 2025.1.4, 2026.0.0 before 2026.0.1.

Is there a fix for CVE-2026-10699?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-10699 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-10699?

Check whether you run Progress MOVEit Transfer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-10699: Progress MOVEit Transfer memory leak in Custom Reports modules

CVE-2026-10699 · Severity: high · CVSS 7.5 · Published 2026-07-08

Progress MOVEit Transfer, a managed file transfer solution used by organizations to securely share sensitive data, contains a vulnerability in its Custom Reports modules. An attacker could exploit this flaw to cause a denial-of-service condition by exhausting system memory. This could lead to service instability or complete outages, preventing legitimate users from accessing or transferring files.

Technologies: Progress MOVEit Transfer. Vendors: Progress.

Quick answers

Is CVE-2026-10699 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-10699 being exploited in the wild.
How severe is CVE-2026-10699?: High severity, with a CVSS score of 7.5, published 8 July 2026.
Which products and versions are affected?: Progress MOVEit Transfer 2025.0.0 before 2025.0.8, 2025.1.0 before 2025.1.4, 2026.0.0 before 2026.0.1.
Is there a fix for CVE-2026-10699?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-10699 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-10699?: Check whether you run Progress MOVEit Transfer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A 'Missing Release of Memory after Effective Lifetime' (CWE-401) vulnerability exists in the Custom Reports modules of Progress MOVEit Transfer. The flaw allows a remote attacker to trigger memory exhaustion on the host system without requiring authentication. By repeatedly invoking specific reporting functions that fail to release memory, an attacker can consume available resources until the service becomes unresponsive or crashes. The issue is fixed in versions 2025.0.8, 2025.1.4, and 2026.0.1.

Affected products

Progress MOVEit Transfer 2025.0.0 before 2025.0.8, 2025.1.0 before 2025.1.4, 2026.0.0 before 2026.0.1

Timeline

2026-07-08: advisory: NVD and vendor advisory published

References

https://community.progress.com/s/article/MOVEit-Transfer-Critical-Security-Bulletin-June-2026

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.