CVE-2026-8488
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 · uneditedAllocation of resources without limits or throttling 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 confidenceThis is a resource exhaustion vulnerability in Progress Software MOVEit Automation where the application fails to properly limit or throttle resource allocation, allowing an attacker to cause excessive memory or resource consumption potentially leading to denial of service. The vulnerability affects specific versions before 2025.0.11 and between 2025.1.0 and 2025.1.7.
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< 2025.0.11>= 2025.1.0, < 2025.1.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine the installed MOVEit Automation versionAccess the MOVEit Automation admin interface and navigate to System > About, or run the product's version check command if available from the command lineAffected if The displayed version falls outside the safe ranges (i.e., version is < 2025.0.11 OR version is >= 2025.1.0 but < 2025.1.7)
-
Confirm the major and minor version numberVerify whether the installation is on the 2025.0.x branch or the 2025.1.x branch by reviewing the full version stringAffected if The version is 2025.0.x where x < 11, or 2025.1.x where x < 7 (i.e., 2025.1.0 through 2025.1.6)
-
Identify if automation workflow components are activeCheck the MOVEit Automation console for any configured automation workflows, scheduled tasks, or resource-intensive operations such as bulk file transfers or batch processing jobsAffected if Automation workflows are defined and active, as the vulnerability resides in the automation workflow components where throttling controls are missing
A user is affected if MOVEit Automation version is either below 2025.0.11 on the 2025.0 branch, or between 2025.1.0 and 2025.1.6 inclusive on the 2025.1 branch, and automation workflow features are in use.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2025.0.112025.1.7
Apply the vendor-supplied patch by upgrading to MOVEit Automation version 2025.0.11 or 2025.1.7 or later to remediate this resource allocation vulnerability.
MOVEit Automation 2025.0.11 or 2025.1.7 (depending on which branch you are upgrading from)
- Identify the currently installed MOVEit Automation version
- If version is < 2025.0.11, upgrade to version 2025.0.11 or later
- If version is >= 2025.1.0 and < 2025.1.7, upgrade to version 2025.1.7 or later
- After upgrade, verify the MOVEit Automation instance is operational
- Test critical workflows to ensure functionality is preserved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8488 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8488 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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