# CVE-2022-46153: Routes exposed with an empty TLSOption in traefik

> Traefik exposes routes with invalid TLS options without verification, allowing bypass of mTLS security controls.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** ECHO-f918-5978-27a9, GHSA-468w-8x39-gj5v, GO-2022-1152

## What is CVE-2022-46153?

CVE-2022-46153 is a high-severity vulnerability in Traefik Traefik, published on 8 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Traefik is an open source HTTP reverse proxy and load balancer. In affected versions there is a potential vulnerability in Traefik managing 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. Users are advised to upgrade to version 2.9.6. Users unable to upgrade should check their logs to detect the error messages and fix your TLS options.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2022-46153?

4 open source packages ship an affected version, including github.com/traefik/traefik/v2 and github.com/traefik/traefik. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/traefik/traefik/v2` | Go | All versions | 2.9.6 |
| `github.com/traefik/traefik/v2` | Go | All versions | 2.9.6 |
| `github.com/traefik/traefik/v2` | Go | All versions | 2.9.6 |
| `github.com/traefik/traefik` | Go | All versions | None |

Products: Traefik Traefik.

## How do I fix CVE-2022-46153?

Upgrade github.com/traefik/traefik/v2 to 2.9.6 or later.

## Is CVE-2022-46153 being exploited?

There is no known exploitation of CVE-2022-46153 in the wild and no public exploit code.

## Other vulnerabilities in Traefik Traefik

- [CVE-2024-45410](https://insights.sbomify.com/CVE-2024-45410/): HTTP client can remove the X-Forwarded headers in Traefik (critical 9.8)
- [CVE-2026-88877](https://insights.sbomify.com/CVE-2026-88877/): Traefik v3.7.0 Authentication Bypass via from-to-www-redirect (critical 9.3)
- [CVE-2026-85595](https://insights.sbomify.com/CVE-2026-85595/): Traefik before v2.11.55 and v3.0.0 through v3.7.10 Authentication Bypass via digestAuth (critical 9.3)
- [CVE-2026-88007](https://insights.sbomify.com/CVE-2026-88007/): Traefik HTTP/3 Backend NTLM Connection Reuse (critical 9.1)
- [CVE-2026-88009](https://insights.sbomify.com/CVE-2026-88009/): Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-46153 and fix it if it is affected.

What it is: CVE-2022-46153 is a high-severity vulnerability in Traefik Traefik, published on 8 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-46153 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.9.6
- github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.9.6
- github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.9.6
- github.com/traefik/traefik (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-46153/ (Markdown: https://insights.sbomify.com/CVE-2022-46153/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-46153
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-46153
- OSV: https://osv.dev/vulnerability/CVE-2022-46153

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-46153/
Summaries are generated and may contain mistakes; the official description above is the record.