Traefik may display authorization header in the debug logs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.5 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N

EPSS

• CVE-2022-23469: 1.04% estimated exploitation activity in the next 30 days; percentile 64.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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: 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.

Published by the source

8 Dec 2022, 16:11 UTC

Last modified by the source

28 Jan 2023, 05:05 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h2ph-vhm7-g4hp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-23469

Advisory: Traefik may display authorization header in the debug logs
IDs: CVE-2022-23469, GHSA-h2ph-vhm7-g4hp
Record: https://patchnext.com/advisories/cve-2022-23469 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/traefik/traefik/v2 2.9.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/traefik/traefik/v2: affected < 2.9.6; fixed in 2.9.6

## Suggested inspection (read-only)
- Go github.com/traefik/traefik/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/traefik/traefik/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h2ph-vhm7-g4hp (GitHub-reviewed advisory GHSA-h2ph-vhm7-g4hp lists affected ranges: Go github.com/traefik/traefik/v2 >=0 <2.9.6)

Commands are suggestions: review each one before running it.