Skip to content

CVE-2026-50149 Contour has Improper JWT Verification for Non-SNI Requests on Virtual Hosts with Fallback Certificate Enabled

MediumCVSS 6.5 EPSS 0.19%
Published
Updated
Exploit status
No public exploit known

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

ProductAffected versionsFixed in
projectcontour contour(Go) >= 1.23.0, < 1.33.5 1.33.5
projectcontour contour = >= 1.23.0, < 1.33.5 No fix listed
redhat/edo/external-dns-rhel8(Red Hat:ext_dns_optr:1) All versions No fix listed
redhat/edo/external-dns-rhel9(Red Hat:ext_dns_optr:1) All versions No fix listed
redhat/openshift4/ose-contour-rhel8(Red Hat:openshift:4) All versions No fix listed

References