Improper Certificate Validation Affecting external-dns package, versions <0.21.0-r3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.19% (8th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-EXTERNALDNS-17897787
  • published9 Jul 2026
  • disclosed19 Aug 2026

Introduced: 9 Jul 2026

CVE-2026-50149  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

Upgrade Minimos:latest external-dns to version 0.21.0-r3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream external-dns package and not the external-dns package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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 Base Scores

version 3.1