Contour 1.26
Contour 1.26
The Contour 1.26 reached end of service life on May 7, 2024 — Contour no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Contour 1.26 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
- contour
- release
- 1.26
- product Label
- Contour
- release Label
- 1.26
- codename
- lts
- latest Version
- 1.26.3
- release Date
- 2023-08-29
- maintained
- source Url
- https://endoflife.date/contour
Lifecycle Dates
- End of Service Life
- May 7, 2024
- Last OEM Support
- May 7, 2024
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Contour 1.26 — 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 Contour 1.26?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Contour 1.26 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.
Contour 1.26 Support: Frequently Asked Questions
Is the Contour 1.26 still supported?
Contour ended support for the Contour 1.26 on May 7, 2024 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Contour 1.26 end of service life (EOSL) date?
Contour lists the end of service life for the Contour 1.26 as May 7, 2024.
Can I keep using the Contour 1.26 after its EOSL date?
Yes. EOSL means Contour 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 Contour 1.26 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Contour 1.26
2 published CVEs affect the Contour 1.26, including 2 rated critical or high severity. Contour no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2026-41246 | HIGH | 8.1 | Apr 23, 2026 | Contour is a Kubernetes ingress controller using Envoy proxy. From v1.19.0 to before v1.33.4, v1.32.5, and v1.31.6, Contour's Cookie Rewriting feature is vulnerable to Lua code injection. An attacker with RBAC permissions to create or modify HTTPProxy resources can craft a malicious value in spec.routes[].cookieRewritePolicies[].pathRewrite.value or spec.routes[].services[].cookieRewritePolicies[].pathRewrite.value that results in arbitrary code execution in the Envoy proxy. The cookie rewriting |
| CVE-2023-44487 | HIGH | 7.5 | Oct 10, 2023 | The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023. |