Is it safe to update Traefik?
Tracking traefik/traefik
Holds breaking changes.
The release notes open with an explicit directive to consult a version-specific migration guide, which is the clearest upstream signal that manual upgrade steps or breaking changes are present. The CORS wildcard and Max-Age behavioral fixes may silently alter responses for existing configurations that happened to rely on the prior (buggy) defaults. The new server options for header underscore removal and max header size may also carry default-value changes that affect running deployments.
What changed
v3.7.6 patches three security CVEs related to HTTP/2 header memory exhaustion and ships a collection of bug fixes across middleware, Kubernetes integrations, and TLS. Notable corrections include CORS Max-Age defaulting incorrectly to zero, CORS wildcard handling when allow-credentials is enabled, and x-forwarded-port in forward-auth. Kubernetes users benefit from Gateway API status fixes, more deterministic EndpointSlice ordering, and ingress-nginx SSL passthrough and force-ssl-redirect corrections. Two new server-level options are introduced: one to strip request headers containing underscores, and one to configure the maximum request header size. A migration guide is explicitly required before upgrading.
Source
Every verdict on Bumplog traces back to a GitHub release. No invented details.
