Rancher 2.15
Rancher 2.15
Third-party support for the SUSE Rancher 2.15: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance — independent of the vendor contract.
24/7 engineers own your Rancher 2.15 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- rancher
- release
- 2.15
- product Label
- Rancher
- release Label
- 2.15
- codename
- lts
- latest Version
- 2.15.3
- release Date
- 2026-08-27
- maintained
- true
- source Url
- https://endoflife.date/rancher
Lifecycle Dates
- End of Service Life
- Feb 27, 2028
- Last OEM Support
- Feb 27, 2027
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Rancher 2.15 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Rancher 2.15?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Rancher 2.15 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Rancher 2.15 Support: Frequently Asked Questions
Is the SUSE Rancher 2.15 still supported?
Yes. The Rancher 2.15 is currently supported by SUSE, and third-party support is available as an alternative — issue management, vulnerability remediation, and compliance help independent of the vendor contract.
When is the SUSE Rancher 2.15 end of service life (EOSL) date?
SUSE lists the end of service life for the Rancher 2.15 as Feb 27, 2028.
Can I keep using the Rancher 2.15 after its EOSL date?
Yes. EOSL means SUSE stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Rancher 2.15 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location. You get an indicative price within 24 hours and a firm quote within 48.
Known Vulnerabilities Affecting Rancher 2.15
5 published CVEs affect the SUSE Rancher 2.15, including 4 rated critical or high severity. Our 24/7 engineers help you assess exposure, prioritize fixes and apply available patches.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2026-71404 | HIGH | 8.7 | Sep 3, 2026 | A flaw was found in Rancher Manager. The GlobalRole controller derived the target ClusterRole name from the user-settable `authz.management.cattle.io/cr-name` annotation and overwrote that object's rules without verifying ownership. A user with delegated GlobalRole create or update permission could point the annotation at any existing ClusterRole, such as `cluster-admin`, and revoke the permissions of every principal bound to it. The change persists after the malicious GlobalRole is deleted. T |
| CVE-2026-75033 | HIGH | 7.7 | Sep 3, 2026 | A flaw was found in Rancher Manager. Project Secrets were propagated into a namespace based only on its `field.cattle.io/projectId` annotation, without verifying that the referenced project belonged to the same downstream cluster. A user able to create namespaces on one cluster could set the annotation to a project ID from another cluster and have that project's secrets copied into a namespace under their control. This issue affects Rancher: before 2.15.1. |
| CVE-2026-75034 | HIGH | 7.4 | Sep 3, 2026 | A flaw was found in Rancher Manager. The SAML assertion replay protection introduced by the fix for CVE-2026-44946 recorded consumed assertion IDs in a per-process cache, so each replica only detected replays that reached the same pod. In a high-availability deployment, an attacker holding a captured assertion could replay it once against every other replica to obtain additional authenticated sessions as the victim. This issue affects Rancher: before 2.15.1. |
| CVE-2026-75035 | HIGH | 7.1 | Sep 3, 2026 | A flaw was found in Rancher Manager. When a non-administrative caller supplied a label selector naming a different user, the ext.cattle.io/v1 Token store dropped its internal owner filter instead of returning an empty result. Any authenticated user could therefore list and watch every other user's tokens, disclosing token metadata and the stored salted hash of the bearer token. This issue affects Rancher: before 2.15.1. |
| CVE-2026-71403 | MEDIUM | 6.1 | Sep 3, 2026 | A flaw was found in Rancher Manager. The /v3/users update path did not enforce immutability of a User resource's `username` and `principalIds` fields. A user holding the `update` verb on `users.management.cattle.io` could inject a foreign identity provider principal into any account, so that the next login by the owner of that principal was bound to the victim's account and inherited its role bindings. This issue affects Rancher: before 2.15.1. |