Quick answers
- Is CVE-2026-88877 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88877 being exploited in the wild.
- How severe is CVE-2026-88877?
- Critical severity, with a CVSS score of 9.8, published 10 September 2026.
- Which products and versions are affected?
- Traefik >= v3.7.0, <= v3.7.11.
- Is there a fix for CVE-2026-88877?
- A patch was published on 2026: Fixed in v3.7.12 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-88877 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-88877?
- Check whether you run Traefik at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass in Traefik's Kubernetes ingress-nginx provider. When an Ingress resource carries both an authentication annotation (e.g., basic-auth) and the nginx.ingress.kubernetes.io/from-to-www-redirect annotation, the provider creates a "sibling" router that matches only on the host with a RedirectRegex middleware but points to the same protected backend service. RedirectRegex is not a terminal handler, so unmatched requests pass through to the backend. The redirect pattern only accepts numeric ports (regex: (https?)://[^/:]+(:[0-9]+)?/(.*)), but Traefik's host matcher canonicalizes authorities via net.SplitHostPort, which accepts non-numeric ports. A request with a malformed port (e.g., Host: www.example.com:x) bypasses the redirect pattern, selects the sibling router lacking all middlewares, and reaches the protected backend unauthenticated. This affects all annotation-derived middlewares: authentication, source-IP allowlisting, and others. Versions >= v3.7.0 and <= v3.7.11 are vulnerable; the fix is available in v3.7.12.
Affected products
- Traefik Traefik >= v3.7.0, <= v3.7.11
Timeline
- 2026-09-10: disclosed: CVE-2026-88877 published
- 2026: patched: Fixed in v3.7.12