HighGHSA-6fwg-jrfw-ff7pCVE-2023-47633GO-2023-2377

Traefik docker container using 100% CPU

Published 5 Dec 2023 · Updated 7 Aug 2026

Is your project on an affected github.com/traefik/traefik/v2?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<2.10.6
Fixed in
2.10.6
Update to the fixed version for your release line, for example:go get github.com/traefik/traefik/v2@v2.10.6
Affected
<3.0.0-beta5
Fixed in
3.0.0-beta5
Update to the fixed version for your release line, for example:go get github.com/traefik/traefik/v3@v3.0.0-beta5

Details

Summary

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.

Details

While attempting to set up Traefik to handle traffic for Docker containers, I observed in the webUI a rule with the following information:

Host(traefik-service) | webwebsecure | traefik-service@docker | traefik-service

I assumed that this is something internal; however, I wondered why it would have a host rule on the web entrypoint configured.

So I have send a request with that hostname with curl -v --resolve "traefik-service:80:xxx.xxx.xxx.xxx" http://traefik-service. That made my whole server unresponsive.

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                                           "/entrypoint.sh trae…"   4 minutes ago       Up 4 minutes   0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 127.0.0.1:8080->8080/tcp   traefik.service

PoC

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 --providers.docker

2. curl -v --resolve "foo:80:127.0.0.1" http://foo

looks like this creates an endless loop of request.

Knowing the name of the docker container seems to be enough to trigger this, if the docker backend is used.

Impact

Server is unreachable and uses 100% CPU

Is GHSA-6fwg-jrfw-ff7p in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/traefik/traefik/v2, and gives you the command that fixes it.

More advisories for github.com/traefik/traefik/v2

  • LowCVE-2026-88012Traefik: respondingTimeouts.readTimeout is not applied to HTTP/3, leaving slow-body uploads unbounded in github.com/traefik/traefik · 16 Sept 2026
  • LowCVE-2026-88011Traefik: ForwardAuth identity spoofing via dot-form header alias in github.com/traefik/traefik · 16 Sept 2026
  • LowCVE-2026-88009Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging in github.com/traefik/traefik · 16 Sept 2026
  • LowCVE-2026-88007Traefik HTTP/3 Backend NTLM Connection Reuse in github.com/traefik/traefik · 16 Sept 2026
  • LowCVE-2026-88004Traefik entrypoint header-name sanitization bypassed via request trailers in github.com/traefik/traefik · 16 Sept 2026
  • LowCVE-2026-88008Traefik: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') and Incorrect Authorization in github.com/traefik/traefik · 16 Sept 2026
All 121 advisories for github.com/traefik/traefik/v2

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.