Traefik Kubernetes CRD allows unauthorized cross-namespace middleware binding
CVE-2026-41174GHSA-xhjw-95fp-8vgq
What to do
Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/traefik/traefik/v3
- Affected
- >= 3.7.0-ea.1, < 3.7.0-rc.2>= 3.0.0-beta1, < 3.6.14
- Fixed in
- 3.7.0-rc.2, 3.6.14
Go github.com/traefik/traefik/v2
- Affected
- < 2.11.43
- Fixed in
- 2.11.43
Go github.com/traefik/traefik
- Affected
- <= 1.7.34
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-xhjw-95fp-8vgq lists affected ranges: Go github.com/traefik/traefik/v3 >=3.7.0-ea.1 =3.0.0-beta1 =0 =0 <=1.7.34
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 4.8 · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N · score source
- EPSS
- CVE-2026-41174: 0.25% estimated exploitation activity in the next 30 days; percentile 16.98 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary There is a vulnerability in Traefik's Kubernetes CRD provider cross-namespace isolation enforcement. When providers.kubernetesCRD.allowCrossNamespace=false, Traefik correctly rejects direct cross-namespace middleware references from IngressRoute objects, but fails to apply the same restriction to middleware references nested inside a Chain middleware's spec.chain.middlewares[]. An actor with permission to create or update Traefik CRDs in their own namespace can exploit this to cause Traefik to resolve and apply middleware objects from another namespace, bypassing the documented isolation boundary. Patches - https://github.com/traefik/traefik/releases/tag/v2.11.43 - https://github.com/traefik/traefik/releases/tag/v3.6.14 - https://github.com/traefik/traefik/releases/tag/v3.7.0-rc.2 For more information If there are any questions or comments about this advisory, please open an issue. <details <summaryOriginal Description</summary Summary When…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-xhjw-95fp-8vgq
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-41174 Advisory: Traefik Kubernetes CRD allows unauthorized cross-namespace middleware binding IDs: CVE-2026-41174, GHSA-xhjw-95fp-8vgq Record: https://patchnext.com/advisories/cve-2026-41174 (revision 1, source checked 26 Oct 2026, 15:20 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 4.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Partial vendor fix; fixed versions by package: github.com/traefik/traefik/v3 3.7.0-rc.2, 3.6.14; github.com/traefik/traefik/v2 2.11.43. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/traefik/traefik/v3: affected >= 3.7.0-ea.1, < 3.7.0-rc.2; >= 3.0.0-beta1, < 3.6.14; fixed in 3.7.0-rc.2, 3.6.14 - Go github.com/traefik/traefik/v2: affected < 2.11.43; fixed in 2.11.43 - Go github.com/traefik/traefik: affected <= 1.7.34 ## Suggested inspection (read-only) - Go github.com/traefik/traefik/v3: check the installed version with your package manager. - Go github.com/traefik/traefik/v2: check the installed version with your package manager. - Go github.com/traefik/traefik: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/traefik/traefik/v3, github.com/traefik/traefik/v2, github.com/traefik/traefik. - 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-xhjw-95fp-8vgq (GitHub-reviewed advisory GHSA-xhjw-95fp-8vgq lists affected ranges: Go github.com/traefik/traefik/v3 >=3.7.0-ea.1 =3.0.0-beta1 =0 =0 <=1.7.34) Commands are suggestions: review each one before running it.
Loading voting…