https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 04:56:16 +0000 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1077 certfr-2025-avi-1077 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1077 https://cve.radiocsirt.org/vuln/euvd-2026-262944 EUVD-2026-262944 https://cve.radiocsirt.org/vuln/euvd-2026-262944 https://cve.radiocsirt.org/vuln/fkie_cve-2025-66491 <p>Traefik is an HTTP reverse proxy and load balancer. Versions 3.5.0 through 3.6.2 have inverted TLS verification logic in the nginx.ingress.kubernetes.io/proxy-ssl-verify annotation. Setting the annotation to &#34;on&#34; (intending to enable backend TLS certificate verification) actually disables verification, allowing man-in-the-middle attacks against HTTPS backends when operators believe they are protected. This issue is fixed in version 3.6.3.</p> <p>Traefik is an HTTP reverse proxy and load balancer. Versions 3.5.0 through 3.6.2 have inverted TLS verification logic in the nginx.ingress.kubernetes.io/proxy-ssl-verify annotation. Setting the annotation to &#34;on&#34; (intending to enable backend TLS certificate verification) actually disables verification, allowing man-in-the-middle attacks against HTTPS backends when operators believe they are protected. This issue is fixed in version 3.6.3.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-66491 https://cve.radiocsirt.org/vuln/ghsa-7vww-mvcr-x6vj <p><strong>Affected:</strong> Go: github.com/traefik/traefik/v3</p> <p>## Impact</p> <p>There is a potential vulnerability in Traefik NGINX provider managing the `nginx.ingress.kubernetes.io/proxy-ssl-verify` annotation.</p> <p>The provider inverts the semantics of the `nginx.ingress.kubernetes.io/proxy-ssl-verify` annotation. Setting the annotation to `&#34;on&#34;` (intending to enable backend TLS certificate verification) actually disables verification, allowing man-in-the-middle attacks against HTTPS backends when operators believe they are protected.</p> <p>## Patches</p> <p>- https://github.com/traefik/traefik/releases/tag/v3.6.3</p> <p>## For more information</p> <p>If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).</p> <p>&lt;details&gt; &lt;summary&gt;Original Description&lt;/summary&gt;</p> <p>### Summary</p> <p>A logic error in Traefik&#39;s experimental ingress-nginx provider inverts the semantics of the `nginx.ingress.kubernetes.io/proxy-ssl-verify` annotation. Setting the annotation to `&#34;on&#34;` (intending to enable backend TLS certificate verification) actually disables verification, allowing man-in-the-middle attacks against HTTPS backends when operators believe they are protected.</p> <p>### Details</p> <p>In `pkg/provider/kubernetes/ingress-nginx/kubernetes.go` at line 512, the `InsecureSkipVerify` field is set using inverted logic:</p> <p>```go nst := &amp;namedServersTransport{ Name: provider.Normalize(namespace + &#34;-&#34; + name), ServersTransport: &amp;dynamic.ServersTransport{ ServerName: ptr.Deref(cfg.ProxySSLName, ptr.Deref(cfg.ProxySSLSe…</p> <p><strong>Affected:</strong> Go: github.com/traefik/traefik/v3</p> <p>## Impact</p> <p>There is a potential vulnerability in Traefik NGINX provider managing the `nginx.ingress.kubernetes.io/proxy-ssl-verify` annotation.</p> <p>The provider inverts the semantics of the `nginx.ingress.kubernetes.io/proxy-ssl-verify` annotation. Setting the annotation to `&#34;on&#34;` (intending to enable backend TLS certificate verification) actually disables verification, allowing man-in-the-middle attacks against HTTPS backends when operators believe they are protected.</p> <p>## Patches</p> <p>- https://github.com/traefik/traefik/releases/tag/v3.6.3</p> <p>## For more information</p> <p>If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).</p> <p>&lt;details&gt; &lt;summary&gt;Original Description&lt;/summary&gt;</p> <p>### Summary</p> <p>A logic error in Traefik&#39;s experimental ingress-nginx provider inverts the semantics of the `nginx.ingress.kubernetes.io/proxy-ssl-verify` annotation. Setting the annotation to `&#34;on&#34;` (intending to enable backend TLS certificate verification) actually disables verification, allowing man-in-the-middle attacks against HTTPS backends when operators believe they are protected.</p> <p>### Details</p> <p>In `pkg/provider/kubernetes/ingress-nginx/kubernetes.go` at line 512, the `InsecureSkipVerify` field is set using inverted logic:</p> <p>```go nst := &amp;namedServersTransport{ Name: provider.Normalize(namespace + &#34;-&#34; + name), ServersTransport: &amp;dynamic.ServersTransport{ ServerName: ptr.Deref(cfg.ProxySSLName, ptr.Deref(cfg.ProxySSLSe…</p> https://cve.radiocsirt.org/vuln/ghsa-7vww-mvcr-x6vj https://cve.radiocsirt.org/vuln/opensuse-su-2026:10020-1 <p>traefik-3.6.6-1.1 on GA media</p> <p>traefik-3.6.6-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10020-1