<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 01:19:07 +0000</lastBuildDate>
    <item>
      <title>cnvd-2022-13371</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2022-13371</link>
      <description>cnvd-2022-13371</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2022-13371</guid>
    </item>
    <item>
      <title>EUVD-2026-234425</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-234425</link>
      <description>EUVD-2026-234425</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-234425</guid>
    </item>
    <item>
      <title>fkie_cve-2022-23632</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-23632</link>
      <description>&lt;p&gt;Traefik is an HTTP reverse proxy and load balancer. Prior to version 2.6.1, Traefik skips the router transport layer security (TLS) configuration when the host header is a fully qualified domain name (FQDN). For a request, the TLS configuration choice can be different than the router choice, which implies the use of a wrong TLS configuration. When sending a request using FQDN handled by a router configured with a dedicated TLS configuration, the TLS configuration falls back to the default configuration that might not correspond to the configured one. If the CNAME flattening is enabled, the selected TLS configuration is the SNI one and the routing uses the CNAME value, so this can skip the expected TLS configuration. Version 2.6.1 contains a patch for this issue. As a workaround, one may add the FDQN to the host rule. However, there is no workaround if the CNAME flattening is enabled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Traefik is an HTTP reverse proxy and load balancer. Prior to version 2.6.1, Traefik skips the router transport layer security (TLS) configuration when the host header is a fully qualified domain name (FQDN). For a request, the TLS configuration choice can be different than the router choice, which implies the use of a wrong TLS configuration. When sending a request using FQDN handled by a router configured with a dedicated TLS configuration, the TLS configuration falls back to the default configuration that might not correspond to the configured one. If the CNAME flattening is enabled, the selected TLS configuration is the SNI one and the routing uses the CNAME value, so this can skip the expected TLS configuration. Version 2.6.1 contains a patch for this issue. As a workaround, one may add the FDQN to the host rule. However, there is no workaround if the CNAME flattening is enabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-23632</guid>
    </item>
    <item>
      <title>GHSA-hrhx-6h34-j5hc — Skip the router TLS configuration when the host header is an FQDN</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hrhx-6h34-j5hc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/traefik/traefik/v2&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;People that configure mTLS between Traefik and clients.&lt;/p&gt;
&lt;p&gt;For a request, the TLS configuration choice can be different than the router choice, which implies the use of a wrong TLS configuration.&lt;/p&gt;
&lt;p&gt;- When sending a request using FQDN handled by a router configured with a dedicated TLS configuration, the TLS configuration falls back to the default configuration that might not correspond to the configured one.&lt;/p&gt;
&lt;p&gt;- If the CNAME flattening is enabled, the selected TLS configuration is the SNI one and the routing uses the CNAME value, so this can skip the expected TLS configuration.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Traefik v2.6.x: https://github.com/traefik/traefik/releases/tag/v2.6.1&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Add the FDQN to the host rule:&lt;/p&gt;
&lt;p&gt;Example:&lt;/p&gt;
&lt;p&gt;```yml
  whoami:
    image: traefik/whoami:v1.7.1
    labels:
      traefik.http.routers.whoami.rule: Host(`whoami.example.com`, `whoami.example.com.`)
      traefik.http.routers.whoami.tls: true
      traefik.http.routers.whoami.tls.options: mtls@file
```&lt;/p&gt;
&lt;p&gt;There is no workaround if the CNAME flattening is enabled.&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/traefik/traefik/v2&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;People that configure mTLS between Traefik and clients.&lt;/p&gt;
&lt;p&gt;For a request, the TLS configuration choice can be different than the router choice, which implies the use of a wrong TLS configuration.&lt;/p&gt;
&lt;p&gt;- When sending a request using FQDN handled by a router configured with a dedicated TLS configuration, the TLS configuration falls back to the default configuration that might not correspond to the configured one.&lt;/p&gt;
&lt;p&gt;- If the CNAME flattening is enabled, the selected TLS configuration is the SNI one and the routing uses the CNAME value, so this can skip the expected TLS configuration.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Traefik v2.6.x: https://github.com/traefik/traefik/releases/tag/v2.6.1&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Add the FDQN to the host rule:&lt;/p&gt;
&lt;p&gt;Example:&lt;/p&gt;
&lt;p&gt;```yml
  whoami:
    image: traefik/whoami:v1.7.1
    labels:
      traefik.http.routers.whoami.rule: Host(`whoami.example.com`, `whoami.example.com.`)
      traefik.http.routers.whoami.tls: true
      traefik.http.routers.whoami.tls.options: mtls@file
```&lt;/p&gt;
&lt;p&gt;There is no workaround if the CNAME flattening is enabled.&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hrhx-6h34-j5hc</guid>
    </item>
    <item>
      <title>gsd-2022-23632</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-23632</link>
      <description>gsd-2022-23632</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-23632</guid>
    </item>
    <item>
      <title>WID-SEC-W-2022-1375 — JFrog Artifactory: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1375</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in JFrog Artifactory ausnutzen, um seine Privilegien zu erweitern, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen und einen Denial-of-Service-Zustand auszulösen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in JFrog Artifactory ausnutzen, um seine Privilegien zu erweitern, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen und einen Denial-of-Service-Zustand auszulösen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1375</guid>
    </item>
  </channel>
</rss>
