dbcve.org
Cyber ProtectApplication · Acronis

CVE-2025-30412

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 improper authentication. 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 · moderate confidence

Improper authentication vulnerability in Acronis Cyber Protect 15 and 16 allows unauthorized actors to access or manipulate sensitive data. The flaw affects both Linux and Windows builds prior to version 16 build 39938 and version 15 build 41800. This is a critical authentication bypass with CVSS 10, enabling complete compromise of the affected systems.

MitigationUpgrade Acronis Cyber Protect 16 to build 39938 or higher, and Acronis Cyber Protect 15 to build 41800 or higher. Prioritize internet-facing installations given the critical severity.

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. Confirm Acronis Cyber Protect installation
    Verify that Acronis Cyber Protect 15 or 16 is installed on the system. On Windows, check Program Files or the Windows Services list for 'Acronis' services. On Linux, check for RPM/DEB packages or running processes related to Acronis.
    Affected if Acronis Cyber Protect 15 or 16 is present on the system.
  2. Identify the installed build version
    Locate the installed build number. In Windows, this is typically accessible through the Acronis product UI under Help > About, or via the Windows Programs and Features list. On Linux, check the installed RPM/DEB package version or query the Cyber Protect agent version using the command line tool if available.
    Affected if The build number cannot be determined or the product is an unpatched version.
  3. Compare against affected build ranges
    For Acronis Cyber Protect 16: verify if the installed build is lower than 39938. For Acronis Cyber Protect 15: verify if the installed build is lower than 41800.
    Affected if Cyber Protect 16 build is below 39938, OR Cyber Protect 15 build is below 41800.
  4. Check if the management interface is internet-facing
    Review network configuration to determine whether the Acronis management console or agent ports are exposed to the internet. This vulnerability is rated critical specifically for internet-facing deployments.
    Affected if The Acronis management interface or agent is accessible from untrusted networks.

A system is affected if it runs Acronis Cyber Protect 16 build lower than 39938 or Cyber Protect 15 build lower than 41800, with priority concern for internet-facing installations given the CVSS 10 authentication bypass severity.

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 higher, and Acronis Cyber Protect 15 to build 41800 or higher. Prioritize internet-facing installations given the critical severity.

Recommended fix High confidence

Acronis Cyber Protect 16 build 39938+ (Linux/Windows) or Cyber Protect 15 build 41800+ (Linux/Windows)

  1. 1. Identify the currently installed Acronis Cyber Protect version and build number
  2. 2. For Cyber Protect 15: Plan upgrade to build 41800 or later
  3. 3. For Cyber Protect 16: Plan upgrade to build 39938 or later
  4. 4. Download the appropriate updated installer from the official Acronis download center or your licensed portal
  5. 5. Review Acronis release notes for the target build for any special upgrade requirements
  6. 6. Back up critical data and configurations before proceeding
  7. 7. Test the upgrade in a non-production environment first
  8. 8. Apply the upgrade following standard Acronis installation procedures
Caveat Review Acronis release notes for the target build; standard precaution - test in non-production before production deployment

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

Fix this in Cyber Protect Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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