Skip to main content
Vulnerability Database/CVE-2025-48960

CVE-2025-48960: Acronis Cyber Protect TLS Encryption Flaw

CVE-2025-48960 involves weak server keys used for TLS encryption in Acronis Cyber Protect 16, potentially exposing encrypted communications to interception. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-48960 Overview

CVE-2025-48960 is a cryptographic weakness in Acronis Cyber Protect 16 where the product uses a weak server key for Transport Layer Security (TLS) encryption. The flaw affects Linux, macOS, and Windows builds before 39938. An attacker positioned on an adjacent network can abuse the weakened cryptography to compromise the integrity of TLS-protected sessions and expose limited confidential data. The weakness is cataloged under CWE-326: Inadequate Encryption Strength.

Critical Impact

An adjacent-network attacker can tamper with TLS traffic to the Acronis Cyber Protect server, undermining the integrity guarantees that protect backup and recovery operations.

Affected Products

  • Acronis Cyber Protect 16 for Linux (builds before 39938)
  • Acronis Cyber Protect 16 for macOS (builds before 39938)
  • Acronis Cyber Protect 16 for Windows (builds before 39938)

Discovery Timeline

  • 2025-06-04 - CVE-2025-48960 published to the National Vulnerability Database
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2025-48960

Vulnerability Analysis

Acronis Cyber Protect 16 ships with a server-side TLS key whose strength does not meet modern cryptographic standards. TLS relies on the server key to authenticate the server and to establish forward-secure session parameters. When that key is weak, the chain of trust that protects session data breaks down. The vulnerability permits high integrity impact against TLS-protected communications while confidentiality impact is limited. Availability of the service is not affected. Exploitation requires an attacker to be positioned on an adjacent network segment and to overcome high attack complexity.

Root Cause

The root cause is inadequate encryption strength in the server key material used for TLS, as described by CWE-326. A key that falls below contemporary strength thresholds reduces the computational effort an attacker needs to forge or manipulate authenticated TLS sessions with the Acronis Cyber Protect server.

Attack Vector

The attack vector is adjacent network, meaning the attacker must share a logically adjacent network with the target such as the same VLAN, Wi-Fi segment, or Layer-2 broadcast domain. From that position, an attacker can intercept, manipulate, or inject TLS traffic destined for the vulnerable Acronis Cyber Protect server. No authentication or user interaction is required. See the Acronis Security Advisory SEC-6403 for vendor-specific technical details.

// No verified exploit code is available for CVE-2025-48960.
// The vulnerability stems from a server key whose strength is
// insufficient to resist cryptographic attack by an adjacent-network adversary.

Detection Methods for CVE-2025-48960

Indicators of Compromise

  • Unexpected TLS handshake renegotiations or certificate presentations from the Acronis Cyber Protect server
  • ARP spoofing, rogue DHCP, or Layer-2 anomalies on network segments hosting Acronis Cyber Protect services
  • Backup or management sessions originating from endpoints not previously enrolled with the Acronis environment

Detection Strategies

  • Inventory all Acronis Cyber Protect 16 installations and record the installed build number to identify systems below build 39938.
  • Inspect TLS certificates and key material presented by Acronis Cyber Protect servers for key sizes or algorithms that fall below current cryptographic guidance.
  • Correlate network telemetry on segments hosting the server for signs of adjacent-network interception attempts.

Monitoring Recommendations

  • Enable packet capture or network detection on the VLANs that carry Acronis Cyber Protect traffic to flag TLS downgrade or handshake anomalies.
  • Alert on changes to Acronis management console authentication patterns, especially from new source addresses.
  • Record and review Acronis Cyber Protect server logs for connection errors tied to certificate validation.

How to Mitigate CVE-2025-48960

Immediate Actions Required

  • Upgrade Acronis Cyber Protect 16 on Linux, macOS, and Windows to build 39938 or later.
  • Restrict management access to the Acronis Cyber Protect server to trusted administrative network segments.
  • Rotate any server keys and certificates that were generated by the vulnerable build after patching.

Patch Information

Acronis addresses the weak TLS server key in Acronis Cyber Protect 16 build 39938. Administrators should consult the Acronis Security Advisory SEC-6403 for complete remediation guidance and download links.

Workarounds

  • Segment the Acronis Cyber Protect server onto a dedicated management VLAN with strict access control lists to reduce adjacent-network exposure.
  • Enforce 802.1X or equivalent network access control on segments hosting the server to limit rogue devices.
  • Monitor Layer-2 integrity using dynamic ARP inspection and DHCP snooping where supported.
bash
# Verify installed Acronis Cyber Protect build on Linux
rpm -qa | grep -i acronis
# or
dpkg -l | grep -i acronis

# After patch deployment, confirm the build number is >= 39938
# before returning the server to production use.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.