CVE-2026-8486
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 Flooding. 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 · high confidenceThis is a resource exhaustion vulnerability in MOVEit Automation where the application fails to properly limit or throttle resource allocation, allowing attackers to flood the system with requests. The lack of throttling controls enables denial-of-service conditions by exhausting CPU, memory, or network resources.
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.
-
Identify installed MOVEit Automation versionLog into the MOVEit Automation web interface and navigate to Help > About or System > Status to view the installed version numberAffected if Version shown is below 2025.0.11, or is 2025.1.0 through 2025.1.6 inclusive
-
Confirm version from system console or configIf web UI is unavailable, check the installation directory for version information or run the MOVEit administrative command-line tool if availableAffected if Cannot confirm the version is 2025.0.11 or 2025.1.7 or later through any available method
-
Assess network accessibility of the serviceDetermine if MOVEit Automation is exposed to network requests from untrusted sources or the internetAffected if The vulnerable version is reachable from networks where attackers could send excessive requests
You are affected if your MOVEit Automation version is less than 2025.0.11, or is between 2025.1.0 and 2025.1.6 inclusive, and the service accepts requests that could be flooded by an attacker
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 patches by upgrading MOVEit Automation to version 2025.0.11 or later, or 2025.1.7 or later, depending on the current version branch in use.
2025.0.11 or 2025.1.7 (depending on your current version branch)
- Identify your current MOVEit Automation version by checking the application or system configuration
- If your version is < 2025.0.11, plan upgrade to 2025.0.11
- If your version is >= 2025.1.0 and < 2025.1.7, plan upgrade to 2025.1.7
- Review the official Progress Software release notes at docs.progress.com for upgrade procedures
- Execute the upgrade following Progress Software's standard upgrade documentation
- After upgrade, verify the installation and test normal operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2026-8486 — 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-8486 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