Is CVE-2026-50149 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-50149 being exploited in the wild.

How severe is CVE-2026-50149?

Medium severity, with a CVSS score of 6.5, published 2 July 2026.

Which products and versions are affected?

github.com/projectcontour/contour (Go) >= 1.23.0, < 1.33.5, SEMVER:introduced=1.23.0,fixed=1.33.5.

Is there a fix for CVE-2026-50149?

Yes. github.com/projectcontour/contour (Go): upgrade to 1.33.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-50149 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-50149?

Check whether you run github.com/projectcontour/contour (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-50149: Project Contour JWT verification bypass in HTTPProxy

Q: Is there a fix for CVE-2026-50149?

Yes. github.com/projectcontour/contour (Go): upgrade to 1.33.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-50149 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-50149?

Check whether you run github.com/projectcontour/contour (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-50149 · Severity: medium · CVSS 6.5 · Published 2026-07-02

Project Contour, a networking tool used to manage traffic in Kubernetes environments, contains a security flaw where identity verification can be bypassed. When specific settings for fallback security certificates and identity tokens are used together, the system fails to enforce security checks for certain types of web requests. This could allow an unauthorized user to access internal services without providing the required credentials, potentially leading to data exposure.

Technologies: github.com/projectcontour/contour (Go). Vendors: Go.

Quick answers

Is CVE-2026-50149 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50149 being exploited in the wild.
How severe is CVE-2026-50149?: Medium severity, with a CVSS score of 6.5, published 2 July 2026.
Which products and versions are affected?: github.com/projectcontour/contour (Go) >= 1.23.0, < 1.33.5, SEMVER:introduced=1.23.0,fixed=1.33.5.
Is there a fix for CVE-2026-50149?: Yes. github.com/projectcontour/contour (Go): upgrade to 1.33.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-50149 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-50149?: Check whether you run github.com/projectcontour/contour (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/projectcontour/contour (Go): upgrade to 1.33.5 or later
```
go get github.com/projectcontour/contour@v1.33.5
```

Technical details

A vulnerability exists in Project Contour's HTTPProxy configuration logic where the simultaneous enablement of '.spec.virtualhost.tls.enableFallbackCertificate' and '.spec.virtualhost.jwtProviders' is not properly validated. When this incompatible configuration is present, requests that do not include a TLS Server Name Indication (SNI) or provide an unrecognized SNI are incorrectly routed to upstream services without undergoing the mandated JWT verification. This allows an unauthenticated attacker to bypass security controls and access protected backend services. The issue is resolved in version 1.33.5, which now rejects such configurations with a 'TLSIncompatibleFeatures' error.

Affected products

Project Contour Contour >= 1.23.0, < 1.33.5

Identifiers

CVE-2026-50149
GHSA-g3xr-5w5j-w4q4
GO-2026-5889

Timeline

2026-05-28: disclosed
2026-07-02: advisory
2026-07-02: patched: Fixed in v1.33.5

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.