Skip to content
fr Sign in
6.5 Medium

CVE-2026-50149 Contour is a Kubernetes ingress controller using Envoy proxy

Description

Contour is a Kubernetes ingress controller using Envoy proxy. In versions 1.23.0 through 1.33.4, when an `HTTPProxy` is configured with incompatible combination of both `.spec.virtualhost.tls.enableFallbackCertificate: true` and `.spec.virtualhost.jwtProviders`, Contour does not reject the configuration. Consequently, requests from clients that do not send TLS SNI or send an unrecognized SNI (one that does not match any `HTTPProxy` FQDN) bypass configured JWT verification and are proxied to upstream services without a valid token. This issue is fixed in Contour v1.33.5. Contour now rejects and marks invalid any `HTTPProxy` resources that combine `.spec.virtualhost.tls.enableFallbackCertificate: true` with `.spec.virtualhost.jwtProviders`. Affected resources will receive a status condition with the error reason `TLSIncompatibleFeatures`. As a workaround, do not enable `.spec.virtualhost.tls.enableFallbackCertificate` on `HTTPProxy` resources that also define `.spec.virtualhost.jwtProviders`. Remove one of the two settings to avoid the invalid configuration.

Affected products and versions

Product Affected versions Fixed in
contour 1.23 1.23.0 → < 1.33.5 1.33.5

References

Timeline

  1. Published
  2. Last modified

Other CVEs of contour

The 5 CVEs of contour →
CVE-2026-41246 Contour is a Kubernetes ingress controller using Envoy proxy 8.1 High CVE-2024-36539 Insecure permissions in contour v1.28.3 allows attackers to access sensitive data and escalate privileges by obtaining… 9.8 Critical CVE-2021-32783 Contour is a Kubernetes ingress controller using Envoy proxy 8.5 High CVE-2020-15127 In Contour ( Ingress controller for Kubernetes) before version 1.7.0, a bad actor can shut down all instances of… 7.5 High
Track this CVE