CVE-2026-8801
Progress Moveit Transfer ≤ 2025.0.8
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-8801 is a low-severity Trailing Space (CWE-46) vulnerability in Progress Moveit Transfer. Its CVSS base score is 3.5 (Low).
Operationally, ranked at the 28th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-42385
Vulnerability Data
Path equivalence: vulnerability in Progress MOVEit Transfer (File Upload modules). This issue affects MOVEit Transfer: before 2025.0.8, from 2025.1.0 before 2025.1.4.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Validating path inputs stops acceptance of trailing-space equivalents before ambiguous resolution can occur.
Proper enforcement of access authorizations structurally blocks the unauthorized file access that the path-equivalence flaw would otherwise enable.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation that prevents path-equivalence flaws.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Application security requirements can mandate input validation for path names, reducing trailing-space equivalence issues.
Secure system architecture and engineering principles include canonicalization and path-handling controls that mitigate ambiguous file names.
Secure coding standards directly require stripping or rejecting trailing spaces in file paths, addressing the root cause.
Security testing in development can detect path-equivalence flaws before deployment.