dbcve.org
Moveit AutomationApplication · Progress

CVE-2026-8485

HIGH · 7.5 CVSS v3.1 Published 2026-05-20
Fix available
A fix is available. Upgrade to 2025.0.11 / 2025.1.7 or later.
See remediation →
84/100
Remediation priority · High
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
Uncontrolled Memory Allocation vulnerability in Progress Software MOVEit Automation allows Excessive Allocation. This issue affects MOVEit Automation: before 2025.0.11, from 2025.1.0 before 2025.1.7.

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

MOVEit Automation suffers from an uncontrolled memory allocation vulnerability where the application fails to properly limit memory usage during certain operations. An unauthenticated attacker could trigger excessive memory allocation, leading to resource exhaustion and denial of service.

MitigationUpgrade MOVEit Automation to version 2025.0.11 or 2025.1.7 or later. If immediate patching is not possible, implement network-level rate limiting and monitor for anomalous memory consumption patterns.

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:< 2025.0.11>= 2025.1.0, < 2025.1.7

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Check MOVEit Automation version via admin console
    Log into the MOVEit Automation admin console and navigate to the System Information or About section to view the installed version number
    Affected if Version displayed is 2025.0.x before 2025.0.11, or version is 2025.1.0 through 2025.1.6
  2. Check MOVEit Automation version via file system
    If admin console access is unavailable, check the installation directory for a version file or check the application binaries for version metadata
    Affected if Version found is 2025.0.x before 2025.0.11, or version is 2025.1.0 through 2025.1.6
  3. Verify network exposure of the web service
    Determine if the MOVEit Automation web interface or API endpoints are accessible from untrusted networks or the internet
    Affected if The service is externally accessible and version is in the affected range

A system is affected if MOVEit Automation version is any 2025.0.x before 2025.0.11 or any version from 2025.1.0 through 2025.1.6, and the service can receive specially crafted requests from attackers.

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.11 / 2025.1.7 or later
Fixed in 2025.0.112025.1.7
Interim mitigation

Upgrade MOVEit Automation to version 2025.0.11 or 2025.1.7 or later. If immediate patching is not possible, implement network-level rate limiting and monitor for anomalous memory consumption patterns.

Recommended fix High confidence

2025.0.11 or 2025.1.7 (depending on which release line you are on)

  1. 1. Identify the currently installed MOVEit Automation version by checking the application or system information
  2. 2. If running a version < 2025.0.11 on the 2025.0.x release line, plan upgrade to version 2025.0.11 or later
  3. 3. If running a version >= 2025.1.0 and < 2025.1.7 on the 2025.1.x release line, plan upgrade to version 2025.1.7 or later
  4. 4. Before upgrading, review the upgrade documentation at docs.progress.com for MOVEit Automation
  5. 5. Perform the upgrade following Progress Software's standard upgrade procedures
  6. 6. After upgrade, verify the new version is running and confirm the vulnerability is remediated
  7. 7. Test critical MOVEit Automation functionality to ensure normal operation

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
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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