CVSS 4.0
7.8 highCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:NHigh (7.8) in traefik traefik. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/traefik/traefik/v3 3.6.11, 3.7.0-ea.2.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:Ngithub.com/traefik/traefik/v3 (Go): fixed in 3.7.0-ea.2, 3.6.11github.com/traefik/traefik/v2 (Go): fixed in 2.11.41Explain CVE-2026-32305 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-32305?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-32305?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-32305 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 NVD's CPE matches.
| Product | Affected |
|---|---|
| traefik:traefik | before 2.11.41 |
| traefik:traefik | from 3.0.0 through 3.6.11 |
| traefik:traefik | 3.7.0:ea1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-wvvq-wgcr-9q48 | Go | github.com/traefik/traefik/v3 | >=3.7.0-ea.1 <3.7.0-ea.2 | 3.7.0-ea.2 |
| GHSA-wvvq-wgcr-9q48 | Go | github.com/traefik/traefik/v3 | <3.6.11 | 3.6.11 |
| GHSA-wvvq-wgcr-9q48 | Go | github.com/traefik/traefik/v2 | <2.11.41 | 2.11.41 |
| GHSA-wvvq-wgcr-9q48 | Go | github.com/traefik/traefik | <=1.7.34 | no fix published |
| GO-2026-4793 | Go | github.com/traefik/traefik | all versions | no fix published |
| GO-2026-4793 | Go | github.com/traefik/traefik/v2 | <2.11.41 | 2.11.41 |
| GO-2026-4793 | Go | github.com/traefik/traefik/v3 | <3.6.11 >=3.7.0-ea.1 <3.7.0-ea.2 | 3.6.11, 3.7.0-ea.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| openSUSE | Leap 15.6 | govulncheck-vulndb | 0.0.20260326T203309-150000.1.155.2 | SUSE-SU-2026:1135-1 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-SU-2026:21483-1 |
| openSUSE | Tumbleweed | traefik | 3.6.12-1.1 | openSUSE-SU-2026:10444-1 |
| openSUSE | Tumbleweed | traefik2 | 2.11.42-1.1 | openSUSE-SU-2026:10445-1 |
From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.
Red Hat rates this Important.
To mitigate unauthorized access, restrict network access to the Traefik instance to only trusted clients and networks. Implement firewall rules to limit inbound connections to the ports Traefik listens on for mTLS-protected services. For example, using `firewalld`, specific source IP addresses or networks can be allowed. After applying firewall rules, ensure the firewall service is reloaded for changes to take effect. This reduces the attack surface by preventing untrusted external access to the Traefik instance.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift Dev Spaces 3.27 | devspaces/traefik-rhel9:1776718585 | Fixed 2026-04-23 | RHSA-2026:10175 |
| Red Hat OpenShift Dev Spaces 3.28 | devspaces/traefik-rhel9:1779786779 | Fixed 2026-05-28 | RHSA-2026:21772 |
| Red Hat OpenShift GitOps | openshift-gitops-1/argo-rollouts-rhel8 | Will not fix |
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-32305.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-287.