dbcve.org
Moveit TransferApplication · Progress

CVE-2026-8651

HIGH · 7.5 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 2025.0.7 / 2025.1.3 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
Limited authentication bypass by spoofing vulnerability in Progress MOVEit Transfer (HTTPS module). This issue affects MOVEit Transfer: before 2025.0.7, from 2025.1.0 before 2025.1.3.

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

A limited authentication bypass vulnerability exists in the HTTPS module of Progress MOVEit Transfer, allowing attackers to potentially spoof authentication credentials and gain unauthorized access by circumventing the normal authentication mechanisms.

MitigationUpgrade MOVEit Transfer to version 2025.0.7 or 2025.1.3 or later to remediate this vulnerability.

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:< 2025.0.7>= 2025.1.1, < 2025.1.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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. Verify MOVEit Transfer is installed
    Check for MOVEit Transfer installation directory or service. Common paths: C:\Program Files\MOVEit Transfer\ or /opt/MOVEit Transfer/. On Windows, also check Services for 'MOVEit Transfer' service.
    Affected if MOVEit Transfer software is present on the system
  2. Determine installed version
    Locate the version information file or check via admin interface. In the installation directory, look for a version.txt, or access the MOVEit Transfer admin web interface and navigate to System > About. The version is typically displayed on the login page footer or in the admin dashboard.
    Affected if Version number cannot be determined or is not visible
  3. Compare version against affected ranges
    Compare your installed version to: < 2025.0.7 OR (>= 2025.1.1 AND < 2025.1.3). For example, versions 2025.0.0 through 2025.0.6 are affected, as are 2025.1.1 and 2025.1.2.
    Affected if Installed version falls within < 2025.0.7 OR >= 2025.1.1 but < 2025.1.3
  4. Confirm HTTPS module is in use
    Check MOVEit Transfer configuration for HTTPS/TLS settings. In the admin interface, go to System > Settings > Network or SSL/TLS configuration. Verify if HTTPS listeners are configured and active.
    Affected if HTTPS module is enabled and configured

If MOVEit Transfer is installed with a version below 2025.0.7 or between 2025.1.1 and 2025.1.2, and the HTTPS module is in use, the environment is likely affected by this authentication bypass vulnerability.

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.7 / 2025.1.3 or later
Fixed in 2025.0.72025.1.3
Interim mitigation

Upgrade MOVEit Transfer to version 2025.0.7 or 2025.1.3 or later to remediate this vulnerability.

Recommended fix High confidence

2025.0.7 or 2025.1.3 (depending on your current branch)

  1. Review the official Progress MOVEit Transfer upgrade documentation at docs.progress.com for detailed upgrade procedures
  2. Ensure you have a complete backup of your MOVEit Transfer configuration and database before upgrading
  3. Download the appropriate fixed version (2025.0.7 or later for 2025.0.x branch, 2025.1.3 or later for 2025.1.x branch) from Progress Software
  4. Follow the standard MOVEit Transfer upgrade process as documented by Progress
  5. After upgrade, verify the authentication mechanism is functioning correctly
  6. Review audit logs to confirm no unauthorized access occurred during the upgrade window

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

Fix this in Moveit Transfer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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