Acronis Cyber Protect 17 · Version Status

Acronis Cyber Protect 17 End of Life Date

Acronis Cyber Protect 17 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (acronis.com); the source of each date is on the product page.

✓ Acronis Cyber Protect 17 is actively supported. No end-of-life date has been announced yet.
EOL Date
TBD
Supported
Latest Release
17 build 43095
Standard release
Release Date
Oct 28, 2025
Acronis Cyber Protect 17 series
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

Acronis Cyber Protect 17 was released on October 28, 2025 and has no published end-of-life date yet. Its most recent patch is 17 build 43095, published September 9, 2026.

← Acronis Cyber Protect 16 All Acronis Cyber Protect versions
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
All Acronis Cyber Protect Versions
VersionLatestEOL DateStatus
10 (Backup and Recovery) — Jun 21, 2013 EOL
11 (Backup and Recovery) — Sep 5, 2014 EOL
11.5 (Backup and Recovery) — May 31, 2019 EOL
11.7 (Acronis Backup) — May 31, 2019 EOL
12 (Acronis Backup) — Sep 9, 2022 EOL
12.5 (Cyber Backup) — Sep 9, 2022 EOL
15 — Feb 21, 2026 EOL
16 — Oct 28, 2027 Active

What does Acronis Cyber Protect 17 end of life mean?

When Acronis Cyber Protect 17 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Acronis Cyber Protect 17 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to Acronis Cyber Protect 17 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Acronis Cyber Protect 17 reach end of life?
Acronis Cyber Protect 17 has no announced end-of-life date yet — it is currently supported, with EOL to be determined.
Is Acronis Cyber Protect 17 still supported?
Yes, Acronis Cyber Protect 17 is currently supported. The EOL date is TBD.
What should I upgrade to from Acronis Cyber Protect 17?
The recommended upgrade from Acronis Cyber Protect 17 is Acronis Cyber Protect 17 — the latest actively supported version. Check the Acronis Cyber Protect full timeline for all supported versions.
What are the security risks of running Acronis Cyber Protect 17 past EOL?
When Acronis Cyber Protect 17 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Acronis Cyber Protect should migrate immediately or implement compensating controls.
Data from the vendor's own lifecycle pages (acronis.com) · Generated at build time · How we source data →