CVE-2026-65601

Traefik before 3.7.7 Namespace Confusion via HTTPRoute ExtensionRef

Published Jul 22, 2026 CVSS 4.0 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
Traefik versions 3.7.0 through 3.7.6 contain a namespace confusion vulnerability in the Kubernetes Gateway API provider. When resolving HTTPRoute.spec.rules[].backendRefs[].filters[].extensionRef, Traefik used the backend Service namespace instead of the HTTPRoute namespace. A low-privileged route author holding a ReferenceGrant for a cross-namespace Service could therefore bind a Traefik Middleware from the backend namespace without a separate grant for that middleware, potentially injecting trusted reverse-proxy identity headers into downstream requests. The issue is fixed in version 3.7.7.

Analysis

AI-generated

Technical impact

Traefik versions 3.7.0 through 3.7.6 incorrectly resolved HTTPRoute.spec.rules[].backendRefs[].filters[].extensionRef by using the backend Service’s namespace instead of the HTTPRoute's namespace. This namespace confusion allows a low‑privileged route author who has a ReferenceGrant to a cross‑namespace Service to bind a Middleware from a different namespace without a separate grant, potentially injecting trusted reverse‑proxy identity headers into downstream requests. The description does not explicitly state that this leads to privilege escalation; however, the inferred consequence is that if downstream services blindly trust those headers, an attacker could achieve impersonation or unauthorized access.

Affected Systems

Traefik 3.7.0 to 3.7.6, implemented as a Kubernetes Gateway API provider, are affected. Any deployment that uses HTTPRoute resources with backend filter extension references can be impacted, as the bug resides in the provider component that processes these references.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity, while the EPSS score of < 1% suggests a very low probability of exploitation at the time of analysis. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires the attacker to have the ability to create or modify HTTPRoute objects and a ReferenceGrant to a cross‑namespace Service, which may not be trivial but is feasible for a low‑privileged route author. The risk is that the injected headers may be trusted by downstream services, potentially enabling impersonation or unauthorized access, but the description does not confirm a guaranteed privilege escalation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Traefik to version 3.7.7 or later to fix the namespace resolution bug
  • Review and restrict ReferenceGrant resources so that only approved namespaces can reference services and middlewares across namespaces, applying the principle of least privilege
  • Verify existing HTTPRoute configurations to ensure that backend filter extension references point to the intended namespaces and remove any misconfigured bindings

Generated by OpenCVE AI on August 3, 2026 at 23:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-qq9q-x9w4-chhj Traefik Gateway API HTTPRoute BackendRef ExtensionRef Namespace Confusion
History
Type Values Removed Values Added
Weaknesses CWE-348
References
Metrics threat_severity

None

cvssV3_1

{'score': 9.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N'}

threat_severity

Important

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Traefik versions 3.7.0 through 3.7.6 contain a namespace confusion vulnerability in the Kubernetes Gateway API provider. When resolving HTTPRoute.spec.rules[].backendRefs[].filters[].extensionRef, Traefik used the backend Service namespace instead of the HTTPRoute namespace. A low-privileged route author holding a ReferenceGrant for a cross-namespace Service could therefore bind a Traefik Middleware from the backend namespace without a separate grant for that middleware, potentially injecting trusted reverse-proxy identity headers into downstream requests. The issue is fixed in version 3.7.7.
Title Traefik before 3.7.7 Namespace Confusion via HTTPRoute ExtensionRef
First Time appeared Traefik
Traefik traefik
Weaknesses CWE-863
CPEs cpe:2.3:a:traefik:traefik:*:*:*:*:*:*:*:*
Vendors & Products Traefik
Traefik traefik
References
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 8, 2026, 3:51 PM
Reserved
Jul 22, 2026, 10:48 AM
Status
Analyzed
Published
Jul 22, 2026, 12:18 PM
Modified
Oct 8, 2026, 4:17 PM
Severity
Important
Public date
Jul 22, 2026, 11:21 AM