CVE-2026-50149
Published:August 19, 2026
Updated:September 24, 2026
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 Packages
github.com/projectcontour/contour (GO):
Affected version(s) >=v1.23.0 <v1.33.5Fix Suggestion:
Update to version v1.33.5Related Resources (4)
Do you need more information?
Contact UsCVSS v4
Base Score:
8.3
Attack Vector
NETWORK
Attack Complexity
HIGH
Attack Requirements
NONE
Privileges Required
NONE
User Interaction
NONE
Vulnerable System Confidentiality
HIGH
Vulnerable System Integrity
LOW
Vulnerable System Availability
NONE
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
6.5
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
LOW
Availability
NONE
Weakness Type (CWE)
Improper Certificate Validation
EPSS
Base Score:
0.15