<?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>Mon, 05 Oct 2026 05:35:44 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-03430</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-03430</link>
      <description>bdu:2024-03430</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-03430</guid>
    </item>
    <item>
      <title>EUVD-2026-204829</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-204829</link>
      <description>EUVD-2026-204829</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-204829</guid>
    </item>
    <item>
      <title>fkie_cve-2023-47633</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-47633</link>
      <description>&lt;p&gt;Traefik is an open source HTTP reverse proxy and load balancer. The traefik docker container uses 100% CPU when it serves as its own backend, which is an automatically generated route resulting from the Docker integration in the default configuration. This issue has been addressed in versions 2.10.6 and 3.0.0-beta5. Users are advised to upgrade. There are no known workarounds for this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Traefik is an open source HTTP reverse proxy and load balancer. The traefik docker container uses 100% CPU when it serves as its own backend, which is an automatically generated route resulting from the Docker integration in the default configuration. This issue has been addressed in versions 2.10.6 and 3.0.0-beta5. Users are advised to upgrade. There are no known workarounds for this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-47633</guid>
    </item>
    <item>
      <title>GHSA-6fwg-jrfw-ff7p — Traefik docker container using 100% CPU</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6fwg-jrfw-ff7p</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/traefik/traefik/v2, Go: github.com/traefik/traefik/v3&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The traefik docker container uses 100% CPU when it serves as its own backend, which is an automatically generated route resulting from the Docker integration in the default configuration.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;While attempting to set up Traefik to handle traffic for Docker containers, I observed in the webUI a rule with the following information:&lt;/p&gt;
&lt;p&gt;`Host(traefik-service) | webwebsecure | traefik-service@docker | traefik-service`&lt;/p&gt;
&lt;p&gt;I assumed that this is something internal; however, I wondered why it would have a host rule on the web entrypoint configured.&lt;/p&gt;
&lt;p&gt;So I have send a request with that hostname with `curl -v --resolve &amp;#34;traefik-service:80:xxx.xxx.xxx.xxx&amp;#34; http://traefik-service`. That made my whole server unresponsive.&lt;/p&gt;
&lt;p&gt;I assume the name comes from a docker container with that name, traefik itself:
```
localhost ~ # docker ps
CONTAINER ID   IMAGE                                                   COMMAND                  CREATED             STATUS         PORTS                                                                                                NAMES
d1414e74aec7   traefik:v2.10                                           &amp;#34;/entrypoint.sh trae…&amp;#34;   4 minutes ago       Up 4 minutes   0.0.0.0:80-&amp;gt;80/tcp, :::80-&amp;gt;80/tcp, 0.0.0.0:443-&amp;gt;443/tcp, :::443-&amp;gt;443/tcp, 127.0.0.1:8080-&amp;gt;8080/tcp   traefik.service
```&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;1. Start traefik with `docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -p 80:80 --name foo -p 8080:8080 traefik:v2.10 --api.insecure=true --p…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/traefik/traefik/v2, Go: github.com/traefik/traefik/v3&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The traefik docker container uses 100% CPU when it serves as its own backend, which is an automatically generated route resulting from the Docker integration in the default configuration.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;While attempting to set up Traefik to handle traffic for Docker containers, I observed in the webUI a rule with the following information:&lt;/p&gt;
&lt;p&gt;`Host(traefik-service) | webwebsecure | traefik-service@docker | traefik-service`&lt;/p&gt;
&lt;p&gt;I assumed that this is something internal; however, I wondered why it would have a host rule on the web entrypoint configured.&lt;/p&gt;
&lt;p&gt;So I have send a request with that hostname with `curl -v --resolve &amp;#34;traefik-service:80:xxx.xxx.xxx.xxx&amp;#34; http://traefik-service`. That made my whole server unresponsive.&lt;/p&gt;
&lt;p&gt;I assume the name comes from a docker container with that name, traefik itself:
```
localhost ~ # docker ps
CONTAINER ID   IMAGE                                                   COMMAND                  CREATED             STATUS         PORTS                                                                                                NAMES
d1414e74aec7   traefik:v2.10                                           &amp;#34;/entrypoint.sh trae…&amp;#34;   4 minutes ago       Up 4 minutes   0.0.0.0:80-&amp;gt;80/tcp, :::80-&amp;gt;80/tcp, 0.0.0.0:443-&amp;gt;443/tcp, :::443-&amp;gt;443/tcp, 127.0.0.1:8080-&amp;gt;8080/tcp   traefik.service
```&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;1. Start traefik with `docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -p 80:80 --name foo -p 8080:8080 traefik:v2.10 --api.insecure=true --p…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6fwg-jrfw-ff7p</guid>
    </item>
    <item>
      <title>gsd-2023-47633</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-47633</link>
      <description>gsd-2023-47633</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-47633</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:13506-1 — traefik-2.10.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:13506-1</link>
      <description>&lt;p&gt;traefik-2.10.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;traefik-2.10.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:13506-1</guid>
    </item>
  </channel>
</rss>
