Veeam: which version until when — and why “supported” means two things

Veeam Backup & Replication 12 stopped getting ordinary updates in November 2025 — and still received patches against critical flaws in March and June 2026. That is not an oversight. Veeam’s lifecycle table has two date columns per version, and only the second one means what most people hear in the words “end of support”.

Two columns, two meanings

End of Fix is the earlier date. After it, Veeam writes, no further updates, patches or hotfixes are created for that version, with exceptions case by case. The version is still fully supported — but if Veeam concludes that your problem is already fixed in a generally available version, you will be required to update to it. Security updates continue during this stage.

End of Support and Security Fixis the later date, and it is the hard one. From that point the version is no longer supported and no longer receives security updates. Both definitions are Veeam’s own, on its product lifecycle page.

One detail on that page decides how you read every number below: the month given is the last month in which the service is still offered — “February 2027” means through the end of February, not the 1st.

The matrix (as of 19/08/2026)

Product names shortened — every row is a Veeam product. Source: Veeam product lifecycle page, retrieved 19/08/2026.

Two things the table does not show. The agents for Linux, macOS, Oracle Solaris and IBM AIX carry different version numbers but the same two end dates as the Windows agent. And the plug-ins for AWS, Azure, Google Cloud, Nutanix AHV and the remaining hypervisors have no lifecycle of their own: they follow Backup & Replication, and every earlier plug-in version enters End of Fix the moment a new one ships.

Why version 12 is still getting patches

Backup & Replication 12 passed End of Fix in November 2025. Since then Veeam has shipped two cumulative patches for it. Build 12.3.2.4465 on 12/03/2026 closed five vulnerabilities, three of them rated 9.9: twice remote code execution on the backup server by an authenticated domain user, once remote code execution as the postgres user by an account holding the Backup Viewer role. Build 12.3.2.4854 in June 2026 closed CVE-2026-44963, rated 9.4, again remote code execution on the backup server by an authenticated domain user. Both are documented in Veeam’s release notes for 12.3.

That is the practical content of the two columns. Staying on 12 through the end of February 2027 is a legitimate decision, not neglect — the security fixes keep coming. What stops is everything else: no new functionality, no fixes for ordinary bugs, and a support case that ends with “upgrade to 13” the moment the fix exists there. The version is supported; your problem may not be.

The case with no successor

Veeam Backup for Microsoft 365 version 8 is the row worth stopping at. Its End of Support is September 2026. Its End of Fix column does not carry a date at all — it says next GA date, meaning the day the next major version ships.

As of 19/08/2026 that day has not happened. The newest build in Veeam’s own build list is 8.5.0.1014 from 29/06/2026, and no version 9 appears anywhere on it. So the end date is fixed and the replacement is not — which is an unusual position to plan an upgrade from, because you cannot schedule a migration to a version that does not exist yet.

Version 7 shows how the placeholder resolves. Its End of Fix is listed as December 2023, and December 2023 is the month version 7a shipped. Read that way, version 8 leaves End of Fix on the day its successor becomes generally available — and reaches the hard date at the end of September 2026 regardless of whether that successor arrived.

Which version are you actually running

For Backup & Replication, the console’s main menu (≡) has it under Help > About — that gives you the build number, not the marketing version. Veeam maps build numbers to versions in KB2680 for Backup & Replication and in KB4106 for Backup for Microsoft 365. Two traps in those lists are worth knowing before you read them.

• Backup for Microsoft 365 has two build numbers per release. Release 8.5 is 8.5.0.1014 in the console and 13.5.0.1014 in the logs. Pull the number out of a log file and you will conclude you are running 13 when you are running 8.5.
• Backup & Replication 13 appears twice. Build 13.0.0.4967 is dated 03/09/2025 and labelled Veeam Software Appliance; build 13.0.1.180 is dated 19/11/2025. That is why some overviews date version 13 to September and Veeam’s lifecycle table says November.

What is missing is the release, not the date

For Backup for Microsoft 365 the end date is settled and printed in Veeam’s table. The piece of information nobody has is the day the successor ships — and that is a release, which is exactly what patchletter watches. Tick the product on its Backup for Microsoft 365 page and you get an email when a new version appears; the newest one on file there is 8.5.0.1014 from 29/06/2026. The same applies to Backup & Replication (13.1.1.18, 13/08/2026) and the Agent for Microsoft Windows (13.1.1.700). The support cycles sit on those same pages where we have them, and the end-of-life overview sorts everything tracked by remaining runway. Free, no account, one-click unsubscribe.

The honest limitation

Veeam publishes months. Aggregated lifecycle databases turn those months into days, and the days do not always agree. endoflife.date — the source patchletter mirrors — puts End of Fix for Backup & Replication 12 at 03/09/2025. That is the date of the first version 13 build, not the November 2025 in Veeam’s own table. For Backup for Microsoft 365 7 it lists End of Support on 28/06/2026 where Veeam’s table says June 2025 — a year apart.

The rule that follows is dull and useful: for anything with a consequence attached — an audit, a contract, a change approval — read the vendor table. For an overview of what runs out first, an aggregated list is fine. And note what patchletter does not do: it reports new releases, not end-of-support dates. The cycles are there to read, but no alarm goes off on the day. Dates move as well — the table above is the state of 19/08/2026, and Veeam is the one who maintains it.

Lifecycle matrix, phase definitions and the note that the stated month is the last month of service: Veeam product lifecycle page, retrieved 19/08/2026. Build numbers and release dates: KB2680 and KB4106. CVE details for the 12.3.2 patches: KB4696. Version 13 release information: KB4738. Tracked version states from our own dataset as of 19/08/2026. Veeam’s own page remains authoritative for every date in this article.