Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2023-47106

Traefik incorrectly processes fragment in the URL, leads to Authorization Bypass

Overview

Published
4 Dec 2023
Modified
17 Jun 2026
Medium CVE
2 Registry packages
2 OS packages
1 Linux distributions
Yes Fix available

Description

Traefik is an open source HTTP reverse proxy and load balancer. When a request is sent to Traefik with a URL fragment, Traefik automatically URL encodes and forwards the fragment to the backend server. This violates RFC 7230 because in the origin-form the URL should only contain the absolute path and the query. When this is combined with another frontend proxy like Nginx, it can be used to bypass frontend proxy URI-based access control restrictions. This vulnerability has been addressed in versions 2.10.6 and 3.0.0-beta5. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

Weakness: CWE-20

Affected packages · 2

Packages affected by CVE-2023-47106
EcosystemPackageVulnerableFixed in
Go github.com/traefik/traefik/v2 <2.10.6 2.10.6
Go github.com/traefik/traefik/v3 <3.0.0-beta5 3.0.0-beta5

Open a package to see all its vulnerabilities.

Operating systems · 2 fixes

openSUSE 1 release · 2 packages

fixed 2
traefik traefik2
openSUSE fixes for CVE-2023-47106
ReleasePackageFixed inAdvisory
Tumbleweed traefik 2.10.7-1.1 openSUSE-SU-2024:13506-1
Tumbleweed traefik2 2.11.5-1.1 openSUSE-SU-2024:14076-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.