CVE-2026-50149

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

July 2, 2026

Last Modified

August 25, 2026

Advisory Details (1)

Auto-updated Aug 19, 2026
Patch available. Sources: github.
github Patch Available

Improper JWT Verification for Non-SNI Requests on Virtual Hosts with Fallback Certificate Enabled · Advisory · projectcontour/contour · GitHub

https://github.com/projectcontour/contour/security/advisories/GHSA-g3xr-5w5j-w4q4

Vendor Advisories for CVE-2026-50149(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/projectcontour/contour—1.33.5—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 03:22 UTCEG score recompute
  4. 2026-08-25 02:20 UTCEG score recompute
  5. 2026-08-24 11:26 UTCEG score recompute
  6. 2026-08-23 12:30 UTCEG score recompute
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 13:38 UTCEG score recompute
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-21 14:45 UTCEG score recompute
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-19 15:32 UTCEG score recompute
  13. 2026-07-30 11:02 UTCEG score recompute
  14. 2026-07-26 13:05 UTCEG score recompute
  15. 2026-07-23 03:18 UTCEG score recompute
  16. 2026-07-02 17:27 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50149?
CVE-2026-50149 is a medium vulnerability published on July 2, 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.…
When was CVE-2026-50149 disclosed?
CVE-2026-50149 was first published in the National Vulnerability Database on July 2, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50149 actively exploited?
CVE-2026-50149 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.8% of all scored CVEs.
What is the CVSS score of CVE-2026-50149?
CVE-2026-50149 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-50149?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50149, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50149

Explore →

Is Your Infrastructure Affected by CVE-2026-50149?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs