CVE-2026-10699

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-08. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 10, 2026

Advisory Details (1)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

Progress Customer Community

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

Vendor Advisories for CVE-2026-10699(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 00:37 UTCEG score recompute
  2. 2026-07-27 00:37 UTCGHSA enrichment
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 12:28 UTCEG score recompute
  6. 2026-07-26 12:28 UTCGHSA enrichment
  7. 2026-07-25 14:17 UTCEPSS rescore
  8. 2026-07-24 14:17 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:04 UTCEG score recompute
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:24 UTCEPSS rescore
  13. 2026-07-20 17:08 UTCEPSS rescore
  14. 2026-07-19 14:30 UTCEPSS rescore
  15. 2026-07-19 02:28 UTCEPSS rescore
  16. 2026-07-18 10:04 UTCEPSS rescore
  17. 2026-07-17 05:26 UTCGHSA enrichment
  18. 2026-07-16 17:18 UTCGHSA enrichment
  19. 2026-07-16 17:02 UTCEPSS rescore
  20. 2026-07-16 05:09 UTCGHSA enrichment
  21. 2026-07-15 17:00 UTCGHSA enrichment
  22. 2026-07-15 16:57 UTCEPSS rescore
  23. 2026-07-15 04:50 UTCGHSA enrichment
  24. 2026-07-15 02:00 UTCEPSS rescore
  25. 2026-07-14 16:42 UTCGHSA enrichment
Show 18 more
  1. 2026-07-14 04:33 UTCGHSA enrichment
  2. 2026-07-13 22:30 UTCEPSS rescore
  3. 2026-07-13 16:24 UTCGHSA enrichment
  4. 2026-07-13 06:12 UTCEPSS rescore
  5. 2026-07-13 04:14 UTCGHSA enrichment
  6. 2026-07-12 16:05 UTCGHSA enrichment
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-12 03:57 UTCGHSA enrichment
  9. 2026-07-11 15:49 UTCGHSA enrichment
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-11 03:41 UTCGHSA enrichment
  12. 2026-07-10 15:33 UTCGHSA enrichment
  13. 2026-07-10 03:23 UTCGHSA enrichment
  14. 2026-07-09 19:10 UTCEPSS rescore
  15. 2026-07-09 15:15 UTCGHSA enrichment
  16. 2026-07-09 03:07 UTCGHSA enrichment
  17. 2026-07-08 14:59 UTCEG score recompute
  18. 2026-07-08 14:57 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10699?
CVE-2026-10699 is a high vulnerability published on July 8, 2026. 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.
When was CVE-2026-10699 disclosed?
CVE-2026-10699 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10699 actively exploited?
CVE-2026-10699 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.5% of all scored CVEs.
What is the CVSS score of CVE-2026-10699?
CVE-2026-10699 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-10699?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10699, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10699

Explore →

Is Your Infrastructure Affected by CVE-2026-10699?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs