Keyfactor Command 26.2 is the current long-term-support (LTS) release. Customers running older versions of Command should review their version's support status and begin planning an upgrade to remain on a fully supported release.
Support for older versions of Keyfactor Command
Keyfactor's standard support policy covers the current Command release and the two previous releases. Versions that fall outside this support window are no longer fully supported.
Beginning November 1, 2026, Command 24.4 and all previous versions will fall outside the standard support window.
After a version reaches the end of its support window:
- Issues are handled on a best-effort basis.
- Standard support SLAs no longer apply.
- The version does not receive fixes for newly disclosed security vulnerabilities.
The longer an environment remains on an unsupported version, the greater the potential security and operational risk.
Reaching the end of the support window does not cause your existing Command environment to stop working or trigger a forced cutover. It changes the level of support and fixes available for that version. Customers can work with their Keyfactor team to plan an upgrade around their own change windows.
Why upgrade to Command 26.2?
Command 26.2 is an LTS release and provides a fully supported foundation for current and future certificate lifecycle management requirements.
The release also introduces capabilities including:
- Orchestrator pooling, which distributes certificate operations across multiple orchestrators and provides automatic failover if one becomes unavailable.
- Centralized trust management, including trust bundles, certificate store mirroring, and automatic public root synchronization.
- A new reporting engine, which currently operates alongside existing Logi reports.
- Updated CSR SAN handling through enrollment pattern settings.
Command 26.2 also provides the foundation for operating at the scale required as certificate lifetimes decrease and organizations prepare for post-quantum migration.
Planning your upgrade
When upgrading an existing deployment, upgrade Keyfactor Command first, followed by your Universal Orchestrators.
Universal Orchestrators are freshly installed rather than upgraded in place. Existing orchestrators can continue operating after the Command upgrade, allowing you to transition them on your schedule. To use orchestrator pooling, install the Command 26.2 version of the Universal Orchestrator and add the orchestrators to a pool.
Your Keyfactor team can help you:
- Confirm prerequisites for your environment
- Plan the upgrade around your change windows
- Determine an appropriate upgrade date
- Review deployment-specific considerations
Next steps
If your environment is running an affected version, contact your Customer Success Manager to review your support window and plan your upgrade to Command 26.2.
For additional information, refer to:
Comments
Article is closed for comments.