Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

Traefik: respondingTimeouts.readTimeout is not applied to HTTP/3, leaving slow-body uploads unbounded

CVE-2026-88012GHSA-7ghq-v6jf-g56c

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/traefik/traefik/v3

    Affected
    >= 3.0.0, < 3.7.12
    Fixed in
    3.7.12

  • Go github.com/traefik/traefik/v2

    Affected
    >= 2.8.2, < 2.11.56
    Fixed in
    2.11.56

  • Go github.com/traefik/traefik

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
  • CVE-2026-88012: 0.52% estimated exploitation activity in the next 30 days; percentile 43.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
  • CVE-2026-88878: 0.42% estimated exploitation activity in the next 30 days; percentile 36.63 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary There is a medium severity vulnerability in Traefik's HTTP/3 entry points: the respondingTimeouts settings were not applied to the HTTP/3 request path. readTimeout in particular is on by default at 60s and is documented as bounding the time to read the entire request including its body, but it is enforced as a deadline on the TCP connection, which cannot reach a QUIC stream, and Traefik's HTTP/3 server was constructed with no timeout of any kind. An unauthenticated client that trickles a request body therefore holds a request open for as long as it chooses, and with it one upstream connection per request, at negligible cost to itself. Backends with bounded connection pools are the practical pressure point. The HTTP/3 path lost these timeouts in v2.8.2, when a quic-go API change removed the embedded http.Server that had carried them; every release from v2.8.2 onward is affected, and releases before v2.8.2 are not. Traefik v2.8.2 through v2.10.x and v3.0 through v3.6 are…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-7ghq-v6jf-g56c

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6454

  3. Revision 1 · created ·

    Published from osv record GHSA-7ghq-v6jf-g56c

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-88012

Advisory: Traefik: respondingTimeouts.readTimeout is not applied to HTTP/3, leaving slow-body uploads unbounded
IDs: CVE-2026-88012, GHSA-7ghq-v6jf-g56c
Record: https://patchnext.com/advisories/cve-2026-88012 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/traefik/traefik/v3 3.7.12; github.com/traefik/traefik/v2 2.11.56. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/traefik/traefik/v3: affected >= 3.0.0, < 3.7.12; fixed in 3.7.12
- Go github.com/traefik/traefik/v2: affected >= 2.8.2, < 2.11.56; fixed in 2.11.56
- Go github.com/traefik/traefik: affected every version

## Suggested inspection (read-only)
- Go github.com/traefik/traefik/v3: check the installed version with your package manager.
- Go github.com/traefik/traefik/v2: check the installed version with your package manager.
- Go github.com/traefik/traefik: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/traefik/traefik/v3, github.com/traefik/traefik/v2, github.com/traefik/traefik.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-7ghq-v6jf-g56c (OSV record GHSA-7ghq-v6jf-g56c lists affected ranges: Go github.com/traefik/traefik/v2 >=2.8.2 =3.0.0 <3.7.12 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6454 (OSV record GO-2026-6454 lists affected ranges: Go github.com/traefik/traefik >=0; Go github.com/traefik/traefik/v2 >=2.8.2 =3.0.0 <3.7.12 (fixed))
- Verified: https://github.com/advisories/GHSA-7ghq-v6jf-g56c (GitHub-reviewed advisory GHSA-7ghq-v6jf-g56c lists affected ranges: Go github.com/traefik/traefik/v2 >=2.8.2 =3.0.0 <3.7.12)

Commands are suggestions: review each one before running it.

Loading voting…