CVE-2026-54765 is an incorrect authorization vulnerability in Traefik's Kubernetes Gateway API provider affecting versions 3.7.0 through 3.7.5. When two accepted HTTPRoutes target the same backend Service and port but specify different backendRef filters, Traefik may resolve them to the same child service and apply one route's filter set to requests received through the other route. This can cause security-sensitive filter-derived context, including tenant identity, authorization context, or other backend-trusted headers, to be associated with the wrong route.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An authorization/context-isolation flaw in Traefik's Kubernetes Gateway API provider. An attacker able to create an accepted HTTPRoute targeting a shared backend Service:port could cause its backendRef filter context, including security-sensitive trusted headers, to be applied to another route's requests, potentially enabling cross-namespace impact when a ReferenceGrant permits cross-namespace targeting.
A medium-severity access control and authorization vulnerability in Traefik's Kubernetes Gateway API provider that can cause backend context or security-sensitive header filters to leak across HTTPRoutes sharing the same backend Service:port.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.