dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-30410

CRITICAL · 9.8 CVSS v3.0 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Sensitive data disclosure and manipulation due to missing authentication. The following products are affected: Acronis Cyber Protect Cloud Agent (Linux, macOS, Windows) before build 39870, Acronis Cyber Protect 16 (Linux, macOS, Windows) before build 39938, Acronis Cyber Protect 15 (Linux, macOS, Windows) before build 41800.

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

Missing authentication in Acronis Cyber Protect agents allows unauthenticated attackers to access and manipulate sensitive data. The vulnerability affects the agent software across Linux, macOS, and Windows platforms in versions prior to build 39870 (Cloud Agent), 39938 (Cyber Protect 16), and 41800 (Cyber Protect 15).

MitigationUpgrade Acronis Cyber Protect Cloud Agent to build 39870 or later, Cyber Protect 16 to build 39938 or later, and Cyber Protect 15 to build 41800 or later to remediate the authentication bypass.

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify Acronis Cyber Protect agent installation
    On Windows, check Control Panel > Programs and Features or run 'wmic product get name,version'. On Linux, run 'rpm -qa | grep -i acronis' or 'dpkg -l | grep -i acronis'. On macOS, run 'system_profiler SPApplicationsDataType | grep -i acronis' or check /Applications folder.
    Affected if Acronis Cyber Protect agent is installed on the system
  2. Determine the exact build number
    Locate the build/version information for the installed Acronis agent. On Windows, right-click the agent in system tray and select About, or check the agent's status window. On Linux, the RPM/DEB package query will show the build number in the version string. On macOS, right-click the application in Applications folder and select Get Info.
    Affected if Unable to determine the build number for comparison
  3. Compare build against vulnerable thresholds
    Match the identified product type (Cloud Agent, Cyber Protect 15, or Cyber Protect 16) to its corresponding vulnerable threshold: Cloud Agent < 39870, Cyber Protect 16 < 39938, or Cyber Protect 15 < 41800.
    Affected if The installed build number is lower than the corresponding fixed build for that product version

You are affected if an Acronis Cyber Protect agent is installed with a build number below 39870 for Cloud Agent, below 39938 for Cyber Protect 16, or below 41800 for Cyber Protect 15.

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 39870 or later, Cyber Protect 16 to build 39938 or later, and Cyber Protect 15 to build 41800 or later to remediate the authentication bypass.

Recommended fix High confidence

Cyber Protect Cloud Agent: build 39870+ | Cyber Protect 16: build 39938+ | Cyber Protect 15: build 41800+

  1. Identify which Acronis product(s) are deployed: Cyber Protect Cloud Agent, Cyber Protect 16, or Cyber Protect 15
  2. Check current build version of each installed agent in your environment
  3. For Acronis Cyber Protect Cloud Agent (Linux, macOS, Windows): upgrade to build 39870 or later
  4. For Acronis Cyber Protect 16 (Linux, macOS, Windows): upgrade to build 39938 or later
  5. For Acronis Cyber Protect 15 (Linux, macOS, Windows): upgrade to build 41800 or later
  6. Verify successful upgrade by confirming the build number matches or exceeds the required threshold
  7. Test that protected workloads and backup/recovery functions operate normally post-upgrade

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
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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