Support lifecycle
This policy covers Citrix SecurSpaces™ deployments that customers host in their own infrastructure. It doesn't cover SecurSpaces Flex, the Citrix-managed service, which always runs the current version and is upgraded by Citrix.
Version numbers
SecurSpaces versions are numbered YYYY.M.minor:
-
YYYY.M identifies the major version by the year and month of its planned release. For example, 2026.9 is the major version planned for September 2026.
-
minor counts the minor versions released for that major version. For example, 2026.9.5 is the fifth minor version of 2026.9.
The release date of a major version is the date its release is announced in What's new.
| Release type | Planned frequency | Contents |
|---|---|---|
| Major | Twice a year, about every six months | New capabilities. Can include breaking or architectural changes. |
| Minor | As needed, within a major version | Mainly bug fixes and security fixes. Can include minor enhancements. Fully compatible with its major version. |
Supported major versions
Citrix supports the current major version (N) and the previous major version (N-1).
A major version stays supported until the later of these two dates:
-
The release date of the second major version after it (N+2).
-
Six months after the release date of the next major version (N+1). This is the six-month minimum.
Because of the six-month minimum, you always have at least six months to upgrade after a new major version is released. If two major versions are released less than six months apart, three major versions can be supported at the same time for a short period.
Citrix doesn't publish separate end-of-maintenance or end-of-life dates for SecurSpaces versions. The end of support for each major version follows from this rule and from the release dates in the release notes.
Minor versions
Within a supported major version, only the latest minor version is supported.
Minor versions are cumulative: each one contains all the fixes from the minor versions before it. Fixes are delivered only as a new minor version of a supported major version. Citrix doesn't ship fixes for earlier minor versions.
When you report an issue, Citrix Support first asks you to install the latest minor version of your major version. If the issue persists, Citrix delivers the fix in a new minor version.
What support includes
A deployment is supported when it runs the latest minor version of a supported major version. A supported deployment receives full support:
-
Bug fixes, delivered in a new minor version.
-
Security fixes, including fixes for vulnerabilities (CVEs), delivered in a new minor version.
-
Technical support from Citrix Support.
When a major version is no longer supported, Citrix no longer provides fixes or support for it. Citrix Support helps only with upgrading to a supported version.
Platform dependencies
Each SecurSpaces release supports the Kubernetes versions and other platform components listed in System requirements. When an upstream component version reaches its own end of life, Citrix can stop supporting it, independently of this policy.
Is a deployment supported
A deployment is supported when both of these are true:
-
Its major version (YYYY.M) is the current or the previous major version, or it's still within six months of the next major version's release.
-
It runs the latest minor version of that major version.
Example timeline
This example applies the policy to earlier SecurSpaces major versions, as if the policy had been in place. The month in each version number is used as its release date. The dates are illustrative, not commitments.
| Major version | Released | Next major version (N+1) | Major version after that (N+2) | Supported until |
|---|---|---|---|---|
| 2025.4 | April 2025 | 2025.10 (October 2025) | 2026.4 (April 2026) | April 2026: six months after N+1, which is also when N+2 was released |
| 2025.10 | October 2025 | 2026.4 (April 2026) | 2026.9 (September 2026) | October 2026: the six-month minimum is later than the N+2 release |
| 2026.4 | April 2026 | 2026.9 (September 2026) | Next major version, planned for about March 2027 | March 2027 (the six-month minimum), or later if the next major version is late |
| 2026.9 | September 2026 | Next major version, planned for about March 2027 | Following major version, planned for about September 2027 | About September 2027 |
2025.10 shows the six-month minimum. 2026.9 was released only five months after 2026.4, so 2025.10, 2026.4 and 2026.9 are all supported from September to October 2026.