dbcve.org
Moveit AutomationApplication · Progress

CVE-2026-4670

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-30
Fix available
A fix is available. Upgrade to 2024.1.8 / 2025.1.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Authentication bypass by primary weakness vulnerability in Progress Software MOVEit Automation allows Authentication Bypass. This issue affects MOVEit Automation: from 2025.0.0 before 2025.0.9, from 2024.0.0 before 2024.1.8, versions prior to 2024.0.0.

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

This is a critical authentication bypass vulnerability in Progress Software MOVEit Automation. Attackers can exploit this flaw to bypass authentication mechanisms and gain unauthorized access to the MOVEit Automation system without valid credentials. The vulnerability stems from a primary weakness in the authentication implementation.

MitigationImmediately upgrade MOVEit Automation to version 2025.0.9 or later, or 2024.1.8 or later. If running versions prior to 2024.0.0, upgrade to a supported patched version. Apply as a high-priority security update given the critical severity and potential for complete system compromise.

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 AutomationApplication
Affected:< 2024.1.8>= 2025.0.0, < 2025.1.5

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

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

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. Locate installed MOVEit Automation version
    Access the MOVEit Automation admin interface and navigate to the About or System Information page, or check the installation directory for version metadata files
    Affected if The displayed version number is lower than 2024.1.8, or is 2025.0.0 through 2025.1.4 inclusive
  2. Compare version against affected ranges
    If you cannot access the admin interface, use command-line tools or check installation logs to retrieve the exact version string (for example: "2025.0.4" or "2024.1.5")
    Affected if Version falls into < 2024.1.8 OR (>= 2025.0.0 AND < 2025.1.5)
  3. Verify authentication mechanism exposure
    Confirm the MOVEit Automation web interface is accessible from network locations where attackers could send authentication requests
    Affected if The login/authentication endpoint is exposed to untrusted networks without additional network-level restrictions

You are affected if your installed MOVEit Automation version is below 2024.1.8, or is between 2025.0.0 and 2025.1.4 inclusive.

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 2024.1.8 / 2025.1.5 or later
Fixed in 2024.1.82025.1.5
Interim mitigation

Immediately upgrade MOVEit Automation to version 2025.0.9 or later, or 2024.1.8 or later. If running versions prior to 2024.0.0, upgrade to a supported patched version. Apply as a high-priority security update given the critical severity and potential for complete system compromise.

Recommended fix High confidence

2024.1.8 (or 2025.0.9 or 2025.1.5 depending on your release track)

  1. 1. Identify the current installed version of MOVEit Automation
  2. 2. For versions 2024.0.0 through 2024.1.7: Upgrade to version 2024.1.8 or later
  3. 3. For versions 2025.0.0 through 2025.0.8: Upgrade to version 2025.0.9 or later
  4. 4. For versions 2025.1.0 through 2025.1.4: Upgrade to version 2025.1.5 or later
  5. 5. For versions prior to 2024.0.0: Upgrade to version 2024.1.8 or later
  6. 6. After upgrade, verify the MOVEit Automation instance is running the patched version
  7. 7. Test authentication functionality to confirm the vulnerability is resolved

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

Fix this in Moveit Automation Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
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,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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