CVSS 4.0
6.9 mediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NMedium (6.9) in traefik traefik. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/traefik/traefik/v2 2.11.56.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Lgithub.com/traefik/traefik/v2 (Go): fixed in 2.11.56github.com/traefik/traefik/v3 (Go): fixed in 3.7.12Explain CVE-2026-88878 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-88878?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-88878?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-88878 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| traefik | from 2.8.2 through 3.7.13 |
| traefik | from 3.0.0 through 3.7.13 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-7ghq-v6jf-g56c | Go | github.com/traefik/traefik/v2 | >=2.8.2 <2.11.56 | 2.11.56 |
| GHSA-7ghq-v6jf-g56c | Go | github.com/traefik/traefik/v3 | >=3.0.0 <3.7.12 | 3.7.12 |
| GO-2026-6454 | Go | github.com/traefik/traefik | all versions | no fix published |
| GO-2026-6454 | Go | github.com/traefik/traefik/v2 | >=2.8.2 <2.11.56 | 2.11.56 |
| GO-2026-6454 | Go | github.com/traefik/traefik/v3 | >=3.0.0 <3.7.12 | 3.7.12 |
Red Hat rates this Important.
A flaw was found in Traefik's HTTP/3 implementation (v2.8.2 through v2.11.55 and v3.0.0 through v3.7.11) where respondingTimeouts settings, specifically readTimeout, are not applied to QUIC streams. On entry points with HTTP/3 enabled, an unauthenticated remote client can trickle request body bytes to keep HTTP/3 streams open indefinitely without triggering timeout deadlines. In environments utilizing affected Traefik components, this allows attackers to exhaust bounded upstream backend connection pools, resulting in a denial of service for legitimate users.
Disable HTTP/3 on all Traefik entry points by removing the entryPoints.<name>.http3 configuration or setting enabled: false. Alternatively, enforce strict request body timeouts and connection limits at an upstream load balancer or network gateway.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift Dev Spaces 3.31 | devspaces/traefik-rhel9:1792464177 | Fixed 2026-10-26 | RHSA-2026:90321 |
| Red Hat OpenShift GitOps | openshift-gitops-1/argo-rollouts-rhel8 | Not affected | |
| Red Hat OpenShift GitOps | openshift-gitops-1/argo-rollouts-rhel9 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-88878.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).