dbcve.org
Cyber ProtectApplication · Acronis

CVE-2025-30416

CRITICAL · 10.0 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 authorization. The following products are affected: Acronis Cyber Protect 16 (Linux, Windows) before build 39938, Acronis Cyber Protect 15 (Linux, 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 authorization vulnerability in Acronis Cyber Protect 15 and 16 allows unauthenticated attackers to disclose and manipulate sensitive data. The vulnerability affects Linux and Windows versions before build 39938 (CP16) and build 41800 (CP15).

MitigationUpgrade Acronis Cyber Protect 16 to build 39938 or later, and Cyber Protect 15 to build 41800 or later. Apply vendor patches through official Acronis update channels.

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
Cyber ProtectApplication
Affected:= 15= 16

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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 installed Acronis Cyber Protect version
    Check the product version through the Acronis management console, or use the Acronis command-line tool (if available) such as 'acronis-version' or check the Windows Programs and Features/Add-Remove Programs for 'Acronis Cyber Protect'. Alternatively, query the installed software via registry on Windows (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\) or package manager on Linux.
    Affected if The installed version is 15.x or 16.x (any build) and the vendor has not yet applied the patch (build 39938 for v16 or build 41800 for v15).
  2. Confirm the management interface is exposed
    Verify that the Acronis Cyber Protect management portal or API endpoint is accessible from the network. This typically runs on port 8443 or 443 for the web console. Check if external access is permitted through firewall rules.
    Affected if The management interface is reachable from untrusted networks without VPN, increasing exposure to unauthenticated attackers.
  3. Review access control configuration
    Inspect the 'Users and Roles' or 'Access Control' settings within the Acronis Cyber Protect admin console. Verify that strict authorization policies are enforced and that no anonymous or guest access is enabled.
    Affected if Anonymous or guest user accounts are enabled, or authorization enforcement is disabled in the security settings.

If the installed Acronis Cyber Protect is version 15 or 16 and the management interface is network-accessible without having applied the vendor patch (build 39938+ for v16, build 41800+ for v15), the environment is likely affected by this authorization bypass.

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 16 to build 39938 or later, and Cyber Protect 15 to build 41800 or later. Apply vendor patches through official Acronis update channels.

Recommended fix High confidence

Acronis Cyber Protect 16 build 39938+ or Cyber Protect 15 build 41800+

  1. 1. Identify the current installed version of Acronis Cyber Protect by checking the build number in the product UI or via command line
  2. 2. For Acronis Cyber Protect 15 users: Upgrade to build 41800 or later
  3. 3. For Acronis Cyber Protect 16 users: Upgrade to build 39938 or later
  4. 4. Download the updated version from the official Acronis portal or use the built-in update mechanism
  5. 5. Apply the upgrade following standard Acronis upgrade procedures
  6. 6. After upgrade, verify the new build number is installed and confirm the authorization controls are in place

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

Fix this in Cyber Protect Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing8.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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