Traefik routes exposed with an empty TLSOption

Exploitation

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

CVSS

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

EPSS

• CVE-2022-46153: 0.53% estimated exploitation activity in the next 30 days; percentile 44.86 (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 managing the TLS connections. A router configured with a not well-formatted TLSOption is exposed with an empty TLSOption. For instance, a route secured using an mTLS connection set with a wrong CA file is exposed without verifying the client certificates. Patches https://github.com/traefik/traefik/releases/tag/v2.9.6 Workarounds Check the logs to detect the following error messages and fix your TLS options: - Empty CA: - Bad CA content (or bad path): - Unknown Client Auth Type: - Invalid cipherSuites - Invalid curvePreferences 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-468w-8x39-gj5v

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

# Patch Next advisory brief: CVE-2022-46153

Advisory: Traefik routes exposed with an empty TLSOption
IDs: CVE-2022-46153, GHSA-468w-8x39-gj5v
Record: https://patchnext.com/advisories/cve-2022-46153 (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: Medium (CVSS 6.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-468w-8x39-gj5v (GitHub-reviewed advisory GHSA-468w-8x39-gj5v lists affected ranges: Go github.com/traefik/traefik/v2 >=0 <2.9.6)

Commands are suggestions: review each one before running it.