dbcve.org
Cyber ProtectApplication · Acronis

CVE-2026-28718

HIGH · 7.5 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 17.0.41186 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
Denial of service due to insufficient input validation in authentication logging. The following products are affected: Acronis Cyber Protect 17 (Linux, 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 17 due to insufficient input validation in the authentication logging component. An attacker could craft malformed authentication data that causes the logging process to fail or consume excessive resources, resulting in service unavailability.

MitigationUpgrade Acronis Cyber Protect 17 to build 41186 or later to remediate this vulnerability. If immediate patching is not possible, consider restricting access to authentication logging interfaces and monitoring for abnormal logging behavior.

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:< 17.0.41186

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine installed Acronis Cyber Protect 17 version
    Open Acronis Cyber Protect management console or check the product About section. Alternatively, locate the product version through Windows Programs and Features or the installation directory.
    Affected if The installed version is below 17.0.41186 (for example, 17.0.41100, 17.0.40050, or any build number lower than 41186).
  2. Verify authentication service is running
    Open Windows Services console (services.msc) and locate the Acronis Cyber Protect service. Confirm its status is Running, or check via command: Get-Service -Name 'Acronis*'
    Affected if The Acronis Cyber Protect service is actively running and processing authentication requests.
  3. Confirm authentication logging is enabled
    Access the Cyber Protect management console, navigate to Settings or Protection settings, and locate the logging or audit configuration section. Look for options related to authentication logging or security event logging.
    Affected if Authentication logging or security audit logging is turned on in the product settings.
  4. Inspect authentication logs for anomalies
    Locate the Acronis logging directory (typically in the product installation folder under 'logs' or 'var/log'). Search authentication-related log files for error entries, crashes, or excessive resource consumption patterns around authentication events.
    Affected if Log files show repeated failures, exceptions, or abnormal patterns in authentication logging entries.

You are affected if Acronis Cyber Protect 17 is installed with a build number lower than 41186 and the authentication logging feature is enabled and operational.

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 17.0.41186 or later
Fixed in 17.0.41186
Interim mitigation

Upgrade Acronis Cyber Protect 17 to build 41186 or later to remediate this vulnerability. If immediate patching is not possible, consider restricting access to authentication logging interfaces and monitoring for abnormal logging behavior.

Recommended fix High confidence

Cyber Protect 17 build 41186 or later

  1. Verify current Acronis Cyber Protect version by checking the product UI or running: acronis-info (Linux) or checking Add/Remove Programs (Windows)
  2. Download Acronis Cyber Protect 17 build 41186 or later from the official Acronis download center or your licensed portal
  3. For Linux: Run the installer with ./CyberProtect17.x86_64 --quiet or follow standard upgrade procedure
  4. For Windows: Run the MSI/EXE installer and follow the upgrade wizard
  5. Ensure backup of current configuration exists before upgrading
  6. After upgrade, verify the build number matches 17.0.41186 or higher in the product UI
Caveat Standard upgrade - review Acronis release notes for any configuration changes between your current build and 41186

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

Fix this in Cyber Protect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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