CyberArk end-of-life versions and upgrade paths
Every CyberArk release has two deadlines: the end of code fixes, then the end of support. Here is where each PAM Self-Hosted version stands in November 2026, and the shortest supported route out of an old one.
The short version
On 15 November 2026, five CyberArk PAM Self-Hosted versions still receive code fixes. Two of them stop receiving fixes within three months, and a sixth version leaves support altogether in December.
- Safe ground: 15.2 (LTS, fixes until July 2029) and 14.6 (LTS, fixes until June 2028).
- Plan now: 14.2 (LTS) loses fixes and standard support in June 2027.
- Urgent: 15.0 stops receiving fixes at the end of December 2026; 14.4 leaves support at the end of December 2026 (its fixes stopped a year ago); 14.0 loses both fixes and support at the end of January 2027.
- Paid time only: 12.6 (LTS) has had no fixes since June 2025 and no standard support since September 2025. Support can be extended for a fee until June 2027.
- Out of support: 13.2, 13.0, 12.2 and everything older.
Each date means the last day of the month shown. The product now appears in the vendor documentation as Idira PAM - Self-Hosted; the rename did not change any date.
Where each version stands
PAM Self-Hosted covers the Vault, PVWA, CPM, PSM, PSM for SSH and PTA. Status on 15 November 2026:
| Version | Level | Released | Fixes until | Support until | Status |
|---|---|---|---|---|---|
| 15.2 | LTS | Jul 2026 | Jul 2029 | Jul 2029paid: Jul 2031 | Current LTS |
| 15.0 | STS | Dec 2025 | Dec 2026 | Dec 2027 | Fixes end Dec 2026 |
| 14.6 | LTS | Jun 2025 | Jun 2028 | Jun 2028paid: Jun 2030 | Supported |
| 14.4 | STS | Dec 2024 | Dec 2025 | Dec 2026 | Support ends Dec 2026 |
| 14.2 | LTS | Jun 2024 | Jun 2027 | Jun 2027paid: Jun 2029 | Supported, plan ahead |
| 14.0 | LTS | Jan 2024 | Jan 2027 | Jan 2027paid: Jan 2029 | Ends Jan 2027 |
| 13.2 | STS | Jun 2023 | Jun 2024 | Jun 2025 | Unsupported |
| 13.0 | STS | Dec 2022 | Dec 2023 | Dec 2025 | Unsupported |
| 12.6 | LTS | Jun 2022 | Jun 2025 | Sep 2025paid: Jun 2027 | Paid extension only |
| 12.2 | LTS | Jul 2021 | Oct 2024 | Oct 2024paid: Jul 2026 | Unsupported |
| 12.1 and older | — | 2021 or earlier | ended | endedby Jun 2025 at the latest | Unsupported |
“Paid” dates require an extended support agreement with the vendor. Dates cover each original release and its patches. Confirm against the official end-of-life page before any decision.
Two deadlines per version
The vendor's policy gives each release two separate dates, and they don't mean the same thing.
- End of development
- The last day the vendor analyses and fixes code for that version. After it, no new fix is produced for that release, security fixes included: the only way to get one is to upgrade.
- End of support
- The last day support handles your tickets for that version, using fixes that already exist. Tickets opened before that date are still handled; nothing new gets engineered.
For security, the first date is the one that counts. A version that sits between the two still has a helpdesk, but any new vulnerability in it stays open.
LTS or STS: why it changes your calendar
Every release is either Long Term Support (LTS) or Standard Term Support (STS). Any release not labelled LTS is STS.
- LTS: about three years of fixes, covering high and critical security issues and critical functional bugs11Recent LTS releases: 12.2 (July 2021), 12.6 (June 2022), 14.0 (January 2024), 14.2 (June 2024), 14.6 (June 2025) and 15.2 (July 2026). Most arrive in June or July.. Support can be extended for a fee; the fixing period cannot.
- STS: about one year of fixes, for critical security issues only, then roughly one more year of support.
Two rules catch teams out. LTS fixes require every PAM component to run the same LTS version. And upgrades are supported from one LTS version to another, or to the latest release. In practice, the sensible target is almost always the current LTS.
Shortest upgrade paths
A version that is still in its development period can normally go straight to a later supported version. Once a release is out of development, the vendor names the furthest version it can reach in one step, and older estates need two or three hops.
| Installed | Furthest direct upgrade | Route to the current LTS (15.2) |
|---|---|---|
| 15.0 | 15.2 | 15.0 → 15.2 |
| 14.6, 14.2, 14.0 | 15.2 | one step to 15.2 |
| 14.4 | 15.0 | 14.4 → 15.0 → 15.2 |
| 13.2 | 14.2 | 13.2 → 14.2 → 15.2 |
| 13.0 | 14.0 | 13.0 → 14.0 → 15.2 |
| 12.6 | 14.6 | 12.6 → 14.6 → 15.2 |
| 12.2 | 14.2 | 12.2 → 14.2 → 15.2 |
| 12.0, 11.7, 11.6 | 12.6 | → 12.6 → 14.6 → 15.2 |
| 12.1, 11.1 to 11.4 | 12.2 | → 12.2 → 14.2 → 15.2 |
| 11.5 | 13.2 (13.0 for the Vault) | → 13.2 / 13.0 → 14.2 / 14.0 → 15.2 |
| 10.10 | 12.6 | → 12.6 → 14.6 → 15.2 |
Each hop means installing the latest patch of the intermediate version, then checking component compatibility before the next one. From a 10.x or 9.x estate the chain gets long enough that building a current platform and migrating accounts to it is often faster and cleaner. That decision deserves real numbers, not a default.
Before you upgrade
- Map every componentVault, PVWA, CPM, PSM, PSMP, PTA and every Credential Provider, with exact versions and patches. Mixed versions are the most common reason an upgrade stalls.
- Check the operating systemsPlatform end of life shortens CyberArk support too: when Red Hat ended maintenance of RHEL 7, PTA 12.2 and 12.6, which only ran on RHEL or CentOS 7, reached end of life on 30 June 2024.
- Read the target's release notesFor instance, Vault clients in 15.2 enforce DNS SRV names that comply with RFC 2782: non-compliant records must be fixed first.
- Re-test what you built yourselfCustom PSM connectors, CPM plugins and REST API scripts are the first things to break between versions.
- Rehearse and keep a way backA timed dry run in a test environment, a fresh Vault backup and a rollback plan for each component.
Credential Providers follow their own calendar. In November 2026 the supported versions are 15.2 (support until June 2028) and 14.2 LTS (until December 2027). 12.6 LTS is on paid extended support only, until June 2027, and 14.0 and 13.0 left support in February 2026.
Privilege Cloud: the connectors have a calendar too
With Privilege Cloud, the vendor keeps the vault up to date, but the components that run in your own network don't update themselves. In the official table, each version of the Privilege Cloud Connector (which carries CPM and PSM) is supported for twelve months after its release; in November 2026, versions 14.8 and 14.9 are the supported ones. The Secure Tunnel follows the same twelve-month pattern.
How we can help
We map your estate against these dates, choose the target version with you, and run the upgrade or the migration: rehearsal, change windows, rollback plan, and post-upgrade checks on rotation, sessions and integrations.
More on how we work: health checks and upgrades, and what the Idira rename changes.
Sources
- Idira (CyberArk) documentation, End-of-life policy: self-hosted products (definitions, LTS and STS, dates).
- Idira (CyberArk) documentation, Considerations when upgrading PAM - Self-Hosted (upgrade compatibility).
- Idira (CyberArk) documentation, End-of-life policy: SaaS agents (Privilege Cloud connectors).
Dates checked on 15 November 2026. We update this page when the vendor changes its tables; the official pages remain the reference.
Questions
End of life, in short
When does CyberArk 12.6 reach end of life?
Code fixes for PAM Self-Hosted 12.6 (LTS) stopped in June 2025 and standard support ended in September 2025. Support can be extended for a fee until June 2027. From 12.6 you can upgrade directly up to 14.6.
When does CyberArk 14.2 reach end of life?
Both the end of development and the end of standard support for 14.2 (LTS) fall in June 2027, with paid extended support available until June 2029.
Can I upgrade CyberArk directly from 12.6 to 14.2?
Yes. The furthest version 12.6 can reach in one step is 14.6, so 14.2 is within reach. Since 14.2 itself loses fixes in June 2027, going to 14.6 and then 15.2 usually makes more sense.
What is the difference between CyberArk LTS and STS versions?
LTS versions get about three years of high and critical security fixes and critical functional fixes, and their support can be extended for a fee. STS versions get about one year of critical security fixes only, then roughly a year of support.
Did the Idira rename change these dates?
No. The same tables now appear in the Idira documentation, where the product is called Idira PAM - Self-Hosted.
● Next step
Tell us about your vaultVersion, size, deadline. We will tell you straight away whether we are the right people for it.