TRAEFIK COVERAGE

Traefik 2.11 and 3.6 are out of support. Your patching does not have to be.

Traefik Proxy 2.11 ended security support on 7 September 2026 and Traefik 3.6 ended on 16 August 2026, leaving 3.7 as the only supported 3.x line. OSSeva patches open source Traefik Proxy 2.11 and 3.6 after end of support, with Critical fixes within 48 hours. It does not patch Traefik Enterprise or Traefik Hub.

Who it is forTeams running Traefik Proxy 2.11 or 3.6 as a reverse proxy, a Docker or Kubernetes ingress, or inside a platform image, that cannot move to the latest minor yet
What you getSigned patched builds on the line you run, with routing and install configuration unchanged. Assure adds an inventory of Traefik instances and an upgrade plan to a supported line.
How it is pricedPer application. Ask for a quote.
What happens nextYou send your work email, we confirm your Traefik version and how it is deployed, and you get a coverage plan.

Reply within 1 business day · No commitment · or book a 15-minute call

Last reviewed

Only your email is required · An engineer replies within 1 business day · No commitment

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

Traefik support status by line, read on 19 November 2026

Statuses are from Traefik's release page. Active support receives any bug fixes, and security support receives only critical bug and security fixes. Last releases are from the traefik/traefik GitHub releases.

LineActive support endedSecurity supportLast release
Traefik 2.1129 Apr 2025EOL 7 Sep 20262.11.63 (13 Nov 2026, after the end date)
Traefik 3.57 Nov 2025EOL 7 Nov 20253.5.6 (7 Nov 2025)
Traefik 3.67 May 2026EOL 16 Aug 20263.6.25 (31 Jul 2026)
Traefik 3.7SupportedSupported3.7.19 (13 Nov 2026)

Traefik 3.0 to 3.4 ended between 15 July 2024 and 23 July 2025. endoflife.date shows the same 2.11, 3.5 and 3.6 end dates. The release page says its dates may change, and 2.11 was still being released after 7 September 2026, so the end date is a support commitment, not the last tag.

Traefik release and support page →endoflife.date Traefik data →Traefik GitHub releases →

Traefik advisories with no 3.6 fix

Each row has a published CVE record and a Traefik GitHub advisory that agree on the affected range. All five are fixed in Traefik 3.7.13, released on 4 September 2026. The last 3.6 release, 3.6.25 from 31 July 2026, is inside every range. For the first three, 2.11.57 also carries the fix.

CVEWhat it isSeverityAffectedFixed in
CVE-2026-88007HTTP/3 entrypoint shares one backend transport, so NTLM and Kerberos connections are reused across clientsCritical2.11.0 to 2.11.56, 3.0.0 to 3.7.122.11.57, 3.7.13
CVE-2026-88008Client Connection: Upgrade and h2c headers are forwarded to the backend, giving request smuggling and an authorization bypassHigh2.11.26 to 2.11.56, 3.4.2 to 3.7.122.11.57, 3.7.13
CVE-2026-88009A rootless HTTP/1 request target is routed as / but forwarded unchanged, bypassing path-scoped routing and middlewareHighup to 2.11.56, 3.0.0 to 3.7.122.11.57, 3.7.13
CVE-2026-88004Entrypoint header-name sanitization is bypassed through request trailersHigh3.2.0 to 3.7.123.7.13
CVE-2026-88010BasicAuth singleflight coalescing reintroduces a username-enumeration timing oracleMedium3.6.11 to 3.7.123.7.13

Published dates are from the CVE records, assigned by GitHub: 10 September 2026 for the first four and 22 September 2026 for CVE-2026-88010. Severities and fixed releases are from the Traefik GitHub advisories GHSA-qqjf-53cj-pwvv, GHSA-w4v4-9rw7-5326, GHSA-f52w-8j3h-j724, GHSA-v67p-phpq-fc8x and GHSA-8fcf-v89g-xpg6. No 3.6 release after 3.6.25 is on GitHub.

Advisory for CVE-2026-88007 →Advisory for CVE-2026-88008 →CVE-2026-88007 record →CVE-2026-88010 record →

What to weigh before moving from 2.11 or 3.6

Traefik's own documents and advisories show that the obvious target, 3.7, has costs of its own.

  • From 2.11, the v2 to v3 migration guide has three steps: update the install configuration and set core.defaultRuleSyntax to v2, roll v3 through production progressively, then convert routers to the v3 rule syntax one at a time. The guide says v3 keeps v2 syntax working in routing configuration, with minimal breaking changes in the install configuration.
  • 3.7 is the only supported 3.x line, and under the support rule in force from 3.6 each minor gets six months from release. 3.7 was released on 5 May 2026 and the release page lists no end date for it, so plan the next move now, not when it ends.
  • The Ingress NGINX provider, added in 3.5, was reworked heavily in 3.7. At least seven Traefik advisories published between 27 August and 12 November 2026 concern it, and every one has an affected range starting at 3.7.0 or later, so none lists 3.6.
  • Moving off 3.6 to 3.7 also takes you from a line with no fix for the five CVEs above to one that has them. 2.11 already has fixes for CVE-2026-88007, CVE-2026-88008 and CVE-2026-88009 in 2.11.57, and CVE-2026-88004 and CVE-2026-88010 do not affect it.
  • Patching first is reasonable when the move needs a rollout across many clusters. OSSeva ships patched 2.11 and 3.6 builds that keep your routing and install configuration as it is.
  • OSSeva patches open source Traefik Proxy only. Traefik Enterprise and Traefik Hub are Traefik Labs products, and OSSeva does not patch them.

Sources: Traefik release page, v2 to v3 migration guide and GitHub security advisories, read on 19 November 2026. Traefik Proxy is MIT licensed per its GitHub repository.

Traefik v2 to v3 migration guide →Traefik security advisories →HAProxy support →Apache Tomcat support →HashiCorp Consul support →

Why now

2.11 security support ended on 7 September 2026

Traefik's release page lists 2.11, the last 2.x line, as ending security support on 7 September 2026. Active support for it ended on 29 April 2025. The page says target dates may change and gives no commitment after that date.

3.6 ended on 16 August 2026, and 3.7 is the only supported 3.x line

Traefik 3.6 left active support on 7 May 2026 and security support on 16 August 2026. Since Traefik 3.6 each minor is supported for six months from release, so every 3.x line has a short life. The last 3.6 release is 3.6.25 from 31 July 2026.

Fixes landed after 3.6 closed, in 3.7 only

Five CVEs published in September 2026, including a critical HTTP/3 NTLM connection reuse flaw, affect 3.6.25 and are fixed in 3.7.13. Three of them also affect 2.11 and were fixed in 2.11.57, three days before its support ended.

Versions covered

All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.

VersionStatusActive CVEs
2.11(Last 2.x line. Security support EOL 7 Sep 2026)EOLSee advisories
3.6(Security support EOL 16 Aug 2026)EOLSee advisories
3.5(EOL 7 Nov 2025. Assessed case by case.)EOLSee advisories
3.7(Supported. No end date published. Assessed case by case.)CurrentSee advisories

Running a Traefik version or build not listed here?

What you get

Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.

OSSeva Patch

Security patches for Traefik Proxy 2.11 and 3.6 after end of support.

  • Backported security fixes for Traefik Proxy 2.11 and 3.6
  • Critical CVEs fixed within 48 hours, High within 7 days
  • Signed artifacts (GPG + Sigstore)
  • CVE disclosure notifications
  • Architecture review
  • 24/7 managed operations
Most popular

OSSeva Assure

Patch plus compliance documentation and an upgrade plan to a supported line.

  • Everything in Patch
  • Inventory of Traefik instances, providers and middlewares in use
  • Upgrade path assessment for 2.11 to 3.x, including the v2 rule syntax compatibility mode
  • SOC 2 / HIPAA attestation package
  • 24/7 reactive support

OSSeva Operate

Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.

  • Everything in Assure
  • 24/7 ingress and proxy monitoring
  • 15-minute P1 incident response SLA
  • Named senior engineer on your account

All tiers priced per cluster/application — not per core.

Compliance library

📄SOC 2 compliance evidence package
Request →
📄Sample Audit Narrative
Request →
📄Pen-Test Report Summary
Request →
📄HIPAA Technical Safeguard Matrix
Request →

Questions

Frequently asked questions

Book a 15-minute call

Is Traefik 2.11 end of life?

Yes. Traefik's release page lists 2.11 security support as ending on 7 September 2026, and active support ended on 29 April 2025. It is the last 2.x line. The project has still tagged 2.11 releases since, such as 2.11.63 on 13 November 2026, but its page promises nothing past 7 September.

When does Traefik 3.6 reach end of life?

It already has. Traefik 3.6 left active support on 7 May 2026 and security support on 16 August 2026. The last 3.6 release is 3.6.25, from 31 July 2026. Traefik 3.7 is the only 3.x line the page lists as supported.

How long is each Traefik 3.x version supported?

Traefik says that from 3.6 every minor version is supported for 6 months from its release date, and that the last minor after a new major is supported for 2 years. Before 3.6 only the latest minor was supported at any time. It also says these target dates may change.

Which Traefik versions does OSSeva patch?

Traefik Proxy 2.11 and 3.6 after end of support. Other versions are assessed case by case through a version coverage check. OSSeva patches open source Traefik Proxy only, not Traefik Enterprise or Traefik Hub.

Who provides Traefik support after end of support?

Traefik's release page gives the end of support for each line on the dates above. Third-party providers, OSSeva among them, patch the lines the project has ended. Ask each which versions it covers.

Does Traefik 3.6 have known vulnerabilities?

Yes. CVE-2026-88004, CVE-2026-88007, CVE-2026-88008, CVE-2026-88009 and CVE-2026-88010 affect Traefik up to 3.7.12, which includes the last 3.6 release, 3.6.25. All five are fixed in 3.7.13, and no later 3.6 release exists.

Can I upgrade from Traefik 2.11 to 3 without rewriting my routes?

Largely. Traefik's v2 to v3 migration guide says v3 keeps backward compatibility with v2 rule syntax in routing configuration, switched on with core.defaultRuleSyntax set to v2, and that the install configuration has a few breaking changes. You can migrate routers one at a time afterwards.

How is OSSeva Traefik support priced?

It is priced per application. Request a quote and a senior engineer replies within 1 business day.

Get a quote

Ready to get Traefik patched and supported?

Tell us your Traefik versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call