Cyber Protect CloudApplication · Acronis

CVE-2021-32581

HIGH · 8.1 CVSS v3.1 Published 2021-08-05
Fix available
A fix is available. Upgrade to 15.0.26653 / 15.0.27009 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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
Acronis True Image prior to 2021 Update 4 for Windows, Acronis True Image prior to 2021 Update 5 for Mac, Acronis Agent prior to build 26653, Acronis Cyber Protect prior to build 27009 did not implement SSL certificate validation.

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

Acronis True Image, Acronis Agent, and Acronis Cyber Protect fail to validate SSL certificates when establishing secure connections. This allows man-in-the-middle attackers to intercept, modify, or spoof communications by impersonating legitimate servers, potentially leading to credential theft, data tampering, or malware injection during backup or protection operations.

MitigationUpdate affected products to the specified versions: Acronis True Image 2021 Update 4 or later for Windows, 2021 Update 5 or later for Mac, Acronis Agent build 26653 or later, or Acronis Cyber Protect build 27009 or later.

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 Protect CloudApplication
Affected:< 15.0.27009
Cyber Protection AgentApplication
Affected:< 15.0.26653
True ImageApplication
Affected:= 2021

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

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 product
    Check installed programs on Windows (Add/Remove Programs, Programs and Features) or Mac (Applications folder, System Preferences > Users & Groups > Login Items) for Acronis True Image, Acronis Cyber Protect, or Acronis Agent
    Affected if Any Acronis product from the affected list is installed
  2. Determine Acronis True Image version (Windows)
    Open Acronis True Image, go to Help > About, or right-click the desktop icon and select Properties > Details to view the version number
    Affected if Version shows 2021 without Update 4 (Windows) or Update 5 (Mac) applied
  3. Determine Acronis Cyber Protect version
    Open Acronis Cyber Protect console, navigate to Help > About, or check the installed program version in Add/Remove Programs
    Affected if Build number is below 27009
  4. Determine Acronis Cyber Protection Agent version
    Check the Agent version in the Acronis management console, or run 'agent_version' command if available via Acronis command-line tool
    Affected if Build number is below 26653
  5. Verify network connectivity configuration
    Check if the Acronis product is configured to connect to remote backup locations, cloud storage, or management servers - examine backup job settings or connection profiles
    Affected if Product is configured for network-based operations (cloud backup, remote management) where SSL validation would be expected but is missing

You are affected if any Acronis True Image 2021, Cyber Protect Cloud before build 27009, or Cyber Protection Agent before build 26653 is installed and configured for network communications.

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.

From vendor data
Upgrade available Upgrade to 15.0.26653 / 15.0.27009 or later
Fixed in 15.0.2665315.0.27009
Interim mitigation

Update affected products to the specified versions: Acronis True Image 2021 Update 4 or later for Windows, 2021 Update 5 or later for Mac, Acronis Agent build 26653 or later, or Acronis Cyber Protect build 27009 or later.

Fix this in Cyber Protect Cloud Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-32581 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2021-32581 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