CVE-2026-50149 is a medium-severity security vulnerability in github.com/projectcontour/contour (go), affecting versions >= 1.23.0, < 1.33.5. It is fixed in 1.33.5.
Impact 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. To list all HTTPProxies with this invalid configuration, run Patches 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. Workarounds 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. References Contour fallback certificate documentation: https://projectcontour.io/docs/main/config/tls-termination/#fallback-certificate Contour JWT verification documentation: https://projectcontour.io/docs/main/config/jwt-verification/
CVE-2026-50149 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (1.33.5). Upgrading removes the vulnerable code path.
go
github.com/projectcontour/contour (>= 1.23.0, < 1.33.5)github.com/projectcontour/contour → 1.33.5 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-50149 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-50149 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-50149 in your environment →Upgrade github.com/projectcontour/contour to 1.33.5 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-50149 is a medium-severity security vulnerability in github.com/projectcontour/contour (go), affecting versions >= 1.23.0, < 1.33.5. It is fixed in 1.33.5.
CVE-2026-50149 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
github.com/projectcontour/contour (go) versions >= 1.23.0, < 1.33.5 is affected.
Yes. CVE-2026-50149 is fixed in 1.33.5. Upgrade to this version or later.
Whether CVE-2026-50149 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade github.com/projectcontour/contour to 1.33.5 or later.