dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-30409

MEDIUM · 5.5 CVSS v3.0 Published 2025-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
Denial of service due to allocation of resources without limits. The following products are affected: Acronis Cyber Protect Cloud Agent (Windows) before build 39904, Acronis Cyber Protect 17 (Windows) before build 41186.

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

A denial of service vulnerability exists in Acronis Cyber Protect Cloud Agent and Cyber Protect 17 for Windows due to improper bounds on resource allocation. An attacker could exhaust system resources by triggering excessive memory, file handle, or other resource allocation without limits, causing the agent or protected system to become unresponsive.

MitigationUpgrade Acronis Cyber Protect Cloud Agent to build 39904 or later, and Cyber Protect 17 to build 41186 or later, to remediate the resource exhaustion vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/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. Verify Acronis Cyber Protect installation
    Open Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programs. Look for 'Acronis Cyber Protect' or 'Acronis Cyber Protect Cloud Agent'.
    Affected if Either Acronis Cyber Protect 17 or Acronis Cyber Protect Cloud Agent is listed as installed.
  2. Identify the specific product variant
    Check the program name in the installed programs list. Acronis Cyber Protect Cloud Agent is the cloud-hosted version, while 'Acronis Cyber Protect 17' is the on-premises version.
    Affected if The installed product is either Acronis Cyber Protect Cloud Agent or Cyber Protect 17 for Windows.
  3. Locate the build version
    In the installed programs list, note the version number displayed next to the Acronis product. Alternatively, open Acronis Cyber Protect console and check About or Help > About, or examine the executable properties of the agent service (commonly in C:\Program Files\Acronis\). Right-click the executable and view 'File version' in the Details tab.
    Affected if A build version is found in the format such as '17.x.x.xxxx' or similar.
  4. Compare build against fixed versions
    Compare your installed build number to the fixed builds: For Cloud Agent, compare to build 39904. For Cyber Protect 17, compare to build 41186. If your build number is LOWER than the respective fixed build, you are running a vulnerable version.
    Affected if The installed build number is below 39904 for Cloud Agent, or below 41186 for Cyber Protect 17.

You are affected if Acronis Cyber Protect Cloud Agent or Cyber Protect 17 for Windows is installed with a build number lower than 39904 (Cloud Agent) or 41186 (Cyber Protect 17), as these earlier builds lack bounds on resource allocation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Acronis Cyber Protect Cloud Agent to build 39904 or later, and Cyber Protect 17 to build 41186 or later, to remediate the resource exhaustion vulnerability.

Recommended fix Moderate confidence

Acronis Cyber Protect Cloud Agent (Windows) build 39904 or later; Acronis Cyber Protect 17 (Windows) build 41186 or later

  1. Identify the currently installed Acronis product and build version on the Windows system (Cyber Protect Cloud Agent or Cyber Protect 17)
  2. Access the Acronis portal or download center to obtain the updated agent/package with the fixed build (39904 for Cloud Agent, 41186 for Cyber Protect 17)
  3. Verify the downloaded package matches the required build number for your product
  4. Schedule the upgrade during a maintenance window to minimize service disruption
  5. Back up critical system state and any relevant configuration data before proceeding
  6. Install the updated Acronis Cyber Protect agent using the standard installation process
  7. Verify the new build number is correctly installed post-upgrade
  8. Confirm the Acronis services are running properly and the agent is communicating with the management console

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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