BIT-contour-2026-50149

See a problem?

Import Source

https://github.com/bitnami/vulndb/tree/main/data/contour/BIT-contour-2026-50149.json

JSON Data

https://api.osv.dev/v1/vulns/BIT-contour-2026-50149

Aliases

Published

2026-08-25T08:38:13.920Z

Modified

2026-08-25T23:48:55.172376066Z

Summary

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

Details

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.

Database specific

{
    "severity": "Medium",
    "cpes": [
        "cpe:2.3:a:projectcontour:contour:*:*:*:*:*:kubernetes:*:*"
    ]
}

References

Affected packages

Bitnami / contour

Package

Name: contour
Purl: pkg:bitnami/contour

Severity

6.5 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N CVSS Calculator

Affected ranges

Type: SEMVER
Events: Introduced

1.23.0

Fixed

1.33.5

Database specific

source

"https://github.com/bitnami/vulndb/tree/main/data/contour/BIT-contour-2026-50149.json"