CVE-2026-71325: Traefik: `allowCrossNamespace=false` bypass via `@kubernetescrd` TraefikService backendRef
Noroxi assessment
Priority: Monitor (action score 19/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: traefik traefik 2.11.54.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to traefik traefik 2.11.54 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Traefik is an open-source edge router that makes publishing services a fun and easy experience. Prior to 2.11.54, 3.6.25, and 3.7.10, cross-namespace @kubernetescrd references are not rejected for TraefikService backend references resolved by the service resolver. A tenant confined by RBAC to a single namespace can therefore bind its own router to a TraefikService owned by another namespace and expose or reroute that namespace's backend, defeating the namespace isolation allowCrossNamespace=false is meant to enforce. This issue is fixed in version 2.11.54, 3.6.25, 3.7.10.
- Published
- Aug 6, 2026
- Updated
- Sep 16, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-653
Report tools
Action score
19
Low priority for now.
- CVSS
- 19 / 40 · 4.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 4.8
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| traefik | traefik | cpe:2.3:a:traefik:traefik |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
traefik traefik
- < 2.11.54, >= 3.0.0, < 3.6.25, >= 3.7.0, < 3.7.10affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- traefik traefikbefore 2.11.54
- traefik traefik3.0.0 and later · before 3.6.25
- traefik traefik3.7.0 and later · up to 3.7.10 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/traefik/traefik | from 0 | — |
| Go | github.com/traefik/traefik | up to and including 1.7.34 | — |
| Go | github.com/traefik/traefik/v2 | before 2.11.54 | 2.11.54 |
| Go | github.com/traefik/traefik/v3 | from 3.0.0 · before 3.6.25 | 3.6.25 |
| Go | github.com/traefik/traefik/v3 | from 3.7.0 · before 3.7.10 | 3.7.10 |
Same product
traefik: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-85595Traefik before v2.11.55 and v3.0.0 through v3.7.10 Authentication Bypass via digestAuth38Monitor
- CVE-2026-88877Traefik v3.7.0 Authentication Bypass via from-to-www-redirect37Monitor
- CVE-2026-88007Traefik HTTP/3 Backend NTLM Connection Reuse36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-67309Aug 1, 2026 · Traefik v3.7.0 Path Traversal via RewriteTarget Authentication Bypass31Monitor
- ← EarlierCVE-2026-71324Aug 6, 2026 · Traefik: Cross-user response poisoning via proxied CONNECT on Traefik's shared backend keep-alive pool28Monitor
- Later →CVE-2026-71326Aug 6, 2026 · Traefik: BasicAuth singleflight key collision allows authenticated identity spoofing8Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| traefik traefik | 2.11.54 · description | Vendor (CNA) |
| Go:github.com/traefik/traefik/v2 | 2.11.54 | Package registry (OSV) |
| Go:github.com/traefik/traefik/v3 | 3.6.25 | Package registry (OSV) |
| Go:github.com/traefik/traefik/v3 | 3.7.10 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-4117498 days apartTraefik Kubernetes CRD allows unauthorized cross-namespace middleware binding19Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0786 · Aug 7, 2026(Traefik Güvenlik Zafiyeti)
Not on record for this CVE: researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-653 · Improper Isolation or CompartmentalizationCVSS vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.