Traefik may display authorization header in the debug logs
Published 8 Dec 2022 · Updated 7 Aug 2026
Is your project on an affected github.com/traefik/traefik/v2?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <2.9.6
- Fixed in
- 2.9.6
go get github.com/traefik/traefik/v2@v2.9.6Details
Impact
There is a potential vulnerability in Traefik displaying the Authorization header in its debug logs.
Traefik uses oxy to provide the following features:
- Round Robin: https://doc.traefik.io/traefik/routing/services/#weighted-round-robin-service
- Buffering: https://doc.traefik.io/traefik/middlewares/http/buffering/
- Circuit Breaker: https://doc.traefik.io/traefik/middlewares/http/circuitbreaker/
- In-Flight Requests: https://doc.traefik.io/traefik/middlewares/http/inflightreq/
In such cases, if the log level is set to DEBUG, the credentials provided using the Authorization header are displayed in the debug logs:
level=debug msg="vulcand/oxy/roundrobin/rr: completed ServeHttp on request" Request="{\\"Method\\":\\"POST\\",\\"URL\\":{\\"Scheme\\":\\"\\",\\"Opaque\\":\\"\\",\\"User\\":null,\\"Host\\":\\"\\",\\"Path\\":\\"/<redacted>/<redacted>\\",\\"RawPath\\":\\"\\",\\"ForceQuery\\":false,\\"RawQuery\\":\\"\\",\\"Fragment\\":\\"\\",\\"RawFragment\\":\\"\\"},\\"Proto\\":\\"HTTP/2.0\\",\\"ProtoMajor\\":2,\\"ProtoMinor\\":0,\\"Header\\":{\\"Authorization\\":[\\"Bearer <token value was here>\\"],\\"Content-Type\\":[\\"application/grpc\\"],\\"Grpc-Accept-Encoding\\":[\\"gzip\\"],\\"Grpc-Timeout\\":[\\"29999886u\\"],\\"Te\\":[\\"trailers\\"],\\"User-Agent\\":[\\"<redacted>\\"],<remainder of log message removed>Patches
https://github.com/traefik/traefik/pull/9574 https://github.com/traefik/traefik/releases/tag/v2.9.6
Workarounds
Set the log level to INFO, WARN, or ERROR.
For more information
If you have any questions or comments about this advisory, please open an issue.
Is GHSA-h2ph-vhm7-g4hp 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
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.