{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-88012 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-88012 is a medium-severity denial of service vulnerability in Traefik Traefik, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-88012 and fix it if it is affected.\n\nWhat it is: CVE-2026-88012 is a medium-severity denial of service vulnerability in Traefik Traefik, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-88012 in the wild and no public exploit code.\n\nAffected product: Traefik Traefik. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-88012/ (Markdown: https://insights.sbomify.com/CVE-2026-88012/index.md)","id":"CVE-2026-88012","markdown":"https://insights.sbomify.com/CVE-2026-88012/index.md","name":"CVE-2026-88012","record":{"aliases":["ECHO-1ace-738a-e251","MINI-62v3-92xp-gvg7","MINI-86c5-ph38-vpcf","MINI-rxh8-xx84-7f79"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"HTTP reverse proxy","requires_auth":"none","summary":"Unauthenticated attackers can exhaust backend resources by sending slow HTTP/3 request bodies, causing denial of service in Traefik.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"traefik","vendor":"traefik"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"Traefik is an open source HTTP reverse proxy and load balancer. From 2.8.2 until 2.11.56 and 3.7.12, HTTP/3 entrypoints do not apply entryPoints..transport.respondingTimeouts.readTimeout because the timeout is enforced on a TCP connection and the HTTP/3 server has no corresponding QUIC stream deadline. An unauthenticated client can use a slow request body, trickling data indefinitely while holding a request and an upstream connection open and exhausting backends with bounded connection pools. This issue is fixed in 2.11.56 and 3.7.12.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Traefik: respondingTimeouts.readTimeout is not applied to HTTP/3, leaving slow-body uploads unbounded","id":"CVE-2026-88012","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"traefik:traefik","products":["traefik:traefik"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"rclone: http backend forwards custom/auth headers to a different host on redirect","id":"CVE-2026-88013"},"packages":[],"prev":{"headline":"Traefik: ForwardAuth identity spoofing via dot-form header alias","id":"CVE-2026-88011"},"products":["traefik"],"published":"2026-09-10","related":[{"cvss_score":9.8,"headline":"HTTP client can remove the X-Forwarded headers in Traefik","id":"CVE-2024-45410","kev_date_added":null,"published":"2024-09-19"},{"cvss_score":9.3,"headline":"Traefik v3.7.0 Authentication Bypass via from-to-www-redirect","id":"CVE-2026-88877","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.3,"headline":"Traefik before v2.11.55 and v3.0.0 through v3.7.10 Authentication Bypass via digestAuth","id":"CVE-2026-85595","kev_date_added":null,"published":"2026-09-04"},{"cvss_score":9.1,"headline":"Traefik HTTP/3 Backend NTLM Connection Reuse","id":"CVE-2026-88007","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":8.8,"headline":"Traefik: Rootless HTTP/1 request-target routes as \"/\" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging","id":"CVE-2026-88009","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":8.8,"headline":"Traefik has a possible vulnerability with the path matchers","id":"CVE-2025-32431","kev_date_added":null,"published":"2025-04-21"},{"cvss_score":8.2,"headline":"Traefik v3.7 Authentication Bypass via TLS Option Conflict","id":"CVE-2026-85596","kev_date_added":null,"published":"2026-09-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-11","vendors":["traefik"]},"summary":"Unauthenticated attackers can exhaust backend resources by sending slow HTTP/3 request bodies, causing denial of service in Traefik.","url":"https://insights.sbomify.com/CVE-2026-88012/"}