VulnerabilityPublished 5 Mar 2026Updated 9 Mar 2026

CVE-2026-28715: Acronis Cyber Protect 17 · Incorrect Authorization

Affects Acronis Cyber Protect 17Source CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 41186 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.0 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 41186

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Acronis Cyber Protect 17 to 41186.

Affected software

Product	Affected	Fixed in
AcronisAcronis Cyber Protect 17	Affected ≥ unspecified, < 41186	Fixed in 41186

AI-suggested

If you cannot patch yet, restrict network access to Acronis Cyber Protect management interfaces by implementing network segmentation, firewall rules, and VPN access controls to limit exposure to trusted administrators only. Enforce the principle of least privilege by reviewing and tightening user permissions within the Acronis environment to minimize the risk of unauthorized access. Conduct regular audits of access logs and monitor for unusual activity that could indicate exploitation attempts. Additionally, consider deploying intrusion detection or prevention systems to identify suspicious network traffic targeting Acronis services. Educate IT and security teams about this vulnerability to ensure rapid response and remediation. Finally, maintain comprehensive backups and incident response plans to mitigate potential impacts if exploitation occurs.

Description

Sensitive information disclosure due to improper authorization checks. The following products are affected: Acronis Cyber Protect 17 (Linux, Windows) before build 41186.

Impact

The primary impact of this vulnerability is the unauthorized disclosure of sensitive information, which can compromise confidentiality within affected organizations. Attackers exploiting this flaw could gain access to backup data, system configurations, or security settings, potentially enabling further attacks such as privilege escalation, lateral movement, or data exfiltration. Since the vulnerability does not affect integrity or availability, direct disruption of services or data manipulation is less likely. However, the exposure of sensitive information in cybersecurity and backup solutions can have severe consequences, including regulatory non-compliance, loss of customer trust, and increased risk of targeted attacks. Organizations relying on Acronis Cyber Protect 17 for critical backup and protection services are particularly at risk. The remote network exploitability and lack of user interaction requirement increase the attack surface and ease of exploitation, potentially affecting large-scale deployments across enterprises worldwide.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

security-advisory.acronis.com/advisories/SEC-5910 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Mar 2026, 19:42 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats