Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain stale valid session token
-
DeliveryReplay token to MOVEit web interface
-
ExploitServer fails to expire session
-
ExecutionResume victim's authenticated session
-
ImpactAccess or exfiltrate transferred files
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V7 - Session Management Session expiration enforcement
|
| Exploitation Conditions | The flaw is CWE-613 Insufficient Session Expiration: MOVEit Transfer does not reliably invalidate user sessions/tokens when it should (e.g. after logout, timeout, or credential change), so a session remains usable past its intended lifetime. The concrete prerequisite - not detailed in the terse vendor description - is that the attacker must first obtain a still-valid session artifact (a token captured in transit, left on a shared or public machine, or not revoked after logout); the CVSS PR:N reflects that the attacker needs no account of their own, only the leftover token. Limiting factors: exploitation depends on a valid session token existing and being reachable by the attacker, which is why realistic risk (and the low EPSS) is lower than the 9.8 implies; it does not grant code execution on its own. |
| Impact | Signals are sharply divided for this CVE. The vendor-assigned CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, 9.8 Critical) describes a trivially remote, unauthenticated, full-compromise flaw, and the SSVC Technical Impact is rated 'total'. However, every exploitation-likelihood signal points the other way: EPSS is only 0.31% (23rd percentile), there is no CISA KEV listing, no public POC was provided, and SSVC explicitly records Exploitation: none and Automatable: no. This is a classic 'high-CVSS, currently-low-real-risk' profile - serious in theory but with no evidence of active or imminent exploitation at analysis time. There is also an internal data conflict worth flagging: the weakness is CWE-613 (Insufficient Session Expiration), which by definition presupposes an attacker who already possesses a session token that should have been invalidated, yet the CVSS vector claims PR:N (no privileges) and A:H (full availability impact). A pure session-expiration flaw rarely yields availability impact, so the 9.8 score with C:H/I:H/A:H appears inflated relative to the CWE - verify the true impact and prerequisites with Progress. Given MOVEit Transfer's history as a mass-exploitation target (Cl0p 2023), this should be patched promptly despite the low EPSS, but it does not currently warrant emergency, drop-everything handling. |
| Exploit ScenarioDerived | An attacker who obtains a MOVEit Transfer session token that the server failed to invalidate - for example a token left active after logout, password change, or on a shared workstation - replays it to resume the victim's authenticated session and access or manipulate transferred files. No public exploit code was identified at the time of analysis, and the reused session is unauthenticated from the attacker's own standpoint per the CVSS vector. Realistic impact is account/session takeover rather than the pre-authentication remote code execution the raw 9.8 might suggest. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 19, 2026
Insufficient session expiration in Progress MOVEit Transfer (versions before 2025.1.6, and 2026.0.0 through 2026.0.3) allows an attacker who obtains a still-valid session artifact - a token captured in transit, left behind on a shared or public workstation, or never revoked after logout or a credential change - to keep using that session beyond its intended lifetime, exposing managed file transfer data and functionality. No account of the attacker's own is required (CVSS PR:N), but exploitation is gated on a valid, reachable leftover token existing, which is why our independent assessment scores it AV:N/AC:H/PR:N/UI:N/C:H/I:H/A:N rather than the vendor's 9.8 - the flaw does not by itself yield code execution or availability impact. There is no confirmed active exploitation (not in CISA KEV), no public exploit code identified at time of analysis, and EPSS is only 0.31% (23rd percentile), so real-world risk is materially lower than the headline score suggests. Patches are available from Progress.
Earlier versions of this analysis (1)
Insufficient session expiration in Progress MOVEit Transfer (versions before 2025.1.6 and 2026.0.0 through 2026.0.3) allows an attacker who obtains a still-valid session identifier to continue using that authenticated session after logout, browser close, or inactivity, exposing and potentially altering data the victim was entitled to access. The flaw is rated 7.5 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H), reflecting a network-reachable, high-complexity attack that depends on a victim having already established a reusable session (UI:R) rather than on forged or brute-forced credentials. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis; the issue is fully addressed by upgrading to MOVEit Transfer 2025.1.6 or 2026.0.4.
RemediationAI
Vendor-released patch: upgrade MOVEit Transfer to 2025.1.6 (for the 2025.1.x branch) or 2026.0.4 (for the 2026.0.x branch) per the Progress critical security bulletin at https://community.progress.com/s/article/MOVEit-Transfer-Critical-Security-Bulletin---September-2026; because the defect is server-side session invalidation, upgrading is the only complete fix and restarting the service after upgrade also flushes existing session state. Where immediate patching is not possible, compensating controls with explicit trade-offs apply: shorten the idle and absolute session timeout settings and force re-authentication for administrative and file-transfer sessions (side effect: more frequent logins for automated and partner workflows, which may break scripted integrations that reuse sessions); force a global session/token invalidation by restarting the MOVEit services or rotating signing and session secrets, which logs out all users and interrupts in-flight transfers; require MFA and terminate sessions on credential or role changes; ensure all access is over TLS with HSTS so tokens cannot be captured in transit, and audit web server and application logs for replayed or concurrent session identifiers from unexpected source IPs or geographies. Reduce token exposure on shared and kiosk endpoints by enforcing private browsing or full browser close on logout. Monitor the Progress advisory and CISA KEV for any change in exploitation status, and note that EPSS is currently low (0.31%), so prioritization can follow standard patch cadence rather than emergency response unless exposure of long-lived tokens is suspected.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-613 (Insufficient Session Expiration), a session-management defect in the web application tier of Progress MOVEit Transfer, the managed file transfer platform widely deployed for SFTP, HTTPS, and EDI-style partner exchanges. Per the CPE data (cpe:2.3:a:progress:moveit_transfer:*:*:*:*:*:*:*:*), the affected component is the MOVEit Transfer application itself across the pre-2025.1.6 branch and the 2026.0.x branch. In a properly implemented design, server-side session state (session identifiers, authentication cookies, and API/SAML-issued tokens) must be invalidated server-side on explicit logout, on idle or absolute timeout, and on credential or privilege changes; this flaw means that invalidation is not reliably performed, so a token captured in transit (e.g., over a misconfigured or intercepted channel), retained in browser history or on a shared/kiosk machine, or leaked via logs can continue to be replayed. Note that because the CVSS vector is PR:N, the attacker does not need their own MOVEit account - the captured session carries the victim's privileges - but the AC:H rating in our independent assessment reflects that the attacker must first obtain a live, unexpired token and reach the service with it, a precondition the terse vendor bulletin does not spell out. The flaw is a confidentiality and integrity exposure over already-authenticated channels; it is not a memory-safety bug, not an authentication bypass, and not a path to remote code execution, and it carries no availability impact in the assessed vector.
Know when Progress gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Session reuse needs a captured not-yet-expired token (AC:H) with no attacker privileges (PR:N), yielding account access (C:H/I:H) but no availability impact (A:N), unlike the vendor's A:H.
Primary rating from Vendor (ProgressSoftware).
CVSS VectorNVD
Lifecycle Timeline
5DescriptionNVD
Insufficient Session Expiration vulnerability in Progress MOVEit Transfer.
This issue affects MOVEit Transfer: before 2025.1.6 and from 2026.0.0 before 2026.0.4.
Executive ViewAI
Progress MOVEit Transfer, a managed file transfer platform commonly used to exchange sensitive business files, carries a critical-rated session-expiration weakness in versions before 2025.1.6 and 2026.0.0 through 2026.0.3. If a still-valid session token is captured or left on a shared workstation, an unauthenticated actor could reuse it to reach transferred data and MFT functions, creating confidentiality and integrity exposure for business partners and regulated-data workflows. Leadership should prioritize remediation because the affected service is trust-boundary software, even though no confirmed active exploitation (CISA KEV) or public exploit code has been identified at time of analysis and the vendor patch is available.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Telerik.Web.UI.dll in Progress Telerik UI for ASP.NET AJAX before R2 2017 SP1 and Sitefinity before 10.0.6412.0 does not
In Flowmon versions prior to 11.1.14 and 12.3.5, an operating system command injection vulnerability has been identified
Unauthenticated remote attackers can access the system through the LoadMaster management interface, enabling arbitrary s
In Progress MOVEit Transfer before 2021.0.6 (13.0.6), 2021.1.4 (13.1.4), 2022.0.4 (14.0.4), 2022.1.5 (14.1.5), and 2023.
In Progress® Telerik® Report Server versions prior to 2024 Q1 (10.0.24.130), a remote code execution attack is possible
In WS_FTP Server versions prior to 8.7.4 and 8.8.2, a pre-authenticated attacker could leverage a .NET deserialization v
SQL injection vulnerability in WrVMwareHostList.asp in Ipswitch WhatsUp Gold 15.02 allows remote attackers to execute ar
The DroneDeleteOldMeasurements implementation in Ipswitch WhatsUp Gold before 16.4 does not properly validate serialized
Unauthenticated remote code execution affects Progress ShareFile Storage Zones Controller versions up to 5.12.3 via unau
In WhatsUp Gold versions released before 2024.0.0, if the application is configured with only a single user, a SQL Injec
In WhatsUp Gold versions released before 2024.0.0, a SQL Injection vulnerability allows an unauthenticated attacker to r
In WhatsUp Gold versions released before 2023.1.3, an unauthenticated Remote Code Execution vulnerability in Progress Wh
EUVD-2026-101155
GHSA-vwr9-5p5q-ghvv
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB