dbcve.org
Moveit AutomationApplication · Progress

CVE-2026-8487

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
Incorrect default permissions vulnerability in Progress Software MOVEit Automation allows Retrieve Embedded Sensitive Data. 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 confidence

MOVEit Automation contains incorrect default permissions that allow unauthorized users to retrieve embedded sensitive data. This is a broken access control vulnerability where the default configuration improperly exposes sensitive information that should be restricted.

MitigationUpgrade MOVEit Automation to version 2025.0.11 or 2025.1.7 or later to remediate the incorrect default permissions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Identify MOVEit Automation installed version
    Locate the installation directory and check the version file, or run the application's version check command from the installation path
    Affected if The version is below 2025.0.11 OR falls between 2025.1.0 and 2025.1.6 (inclusive)
  2. Locate sensitive data storage configuration
    Examine the application configuration files for settings related to embedded data storage, temporary files, or sensitive information repositories
    Affected if Default permissions allow unrestricted access to sensitive data directories or files
  3. Verify default access control settings
    Inspect the application's permission configuration (often in config files under the installation directory, look for permissions, access control, or security-related XML/JSON settings)
    Affected if Default settings permit unauthenticated or unauthorized users to read sensitive embedded data
  4. Test for unauthorized data retrieval
    Attempt to access sensitive endpoints or data paths using an account without elevated privileges to confirm if default permissions allow such access
    Affected if A standard user account can retrieve sensitive information that should require elevated permissions

You are affected if MOVEit Automation is running a version below 2025.0.11 or between 2025.1.0-2025.1.6 AND the default permission configuration has not been hardened to restrict access to sensitive data.

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 to remediate the incorrect default permissions.

Recommended fix High confidence

Upgrade to MOVEit Automation 2025.0.11 (or later 2025.0.x) OR 2025.1.7 (or later 2025.1.x)

  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, plan upgrade to version 2025.0.11 or later in the 2025.0.x branch.
  3. 3. If running version >= 2025.1.0 and < 2025.1.7, plan upgrade to version 2025.1.7 or later in the 2025.1.x branch.
  4. 4. Review the official Progress Software release notes at docs.progress.com for upgrade procedures specific to your version.
  5. 5. Perform a backup of the current MOVEit Automation configuration and data before upgrading.
  6. 6. Apply the upgrade following the vendor's documented installation or upgrade process.
  7. 7. After upgrade, verify that the default permissions have been corrected and the vulnerability is resolved.
  8. 8. Test that MOVEit Automation functions normally after the upgrade.
Caveat Review release notes for any breaking changes between your current version and the target fixed version

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

Fix this in Moveit Automation Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing5.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,050
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,280.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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