Insufficient Compartmentalization Affecting traefik-2 package, versions *


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.01% (2nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-TRAEFIK2-16299408
  • published26 Apr 2026
  • disclosed30 Apr 2026

Introduced: 26 Apr 2026

NewCVE-2026-41174  (opens in a new tab)
CWE-653  (opens in a new tab)
CWE-863  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest traefik-2.

NVD Description

Note: Versions mentioned in the description apply only to the upstream traefik-2 package and not the traefik-2 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is a potential 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. This issue has been patched in versions 2.11.43, 3.6.14, and 3.7.0-rc.2.

CVSS Base Scores

version 3.1