Amazon aws-load-balancer-controller
Cross-namespace traffic interception via incorrect route precedence ordering in AWS Load Balancer Controller
Edge device · Load balancer / ADCproduct or title mentions "load balancer" (medium confidence)
Incorrect behavior order in the Gateway API listener-rule generation in Amazon AWS Load Balancer Controller before 3.4.2 might allow an authenticated remote user to intercept, spoof, or deny another namespace's gRPC traffic on a shared Gateway via a crafted HTTPRoute resource. To mitigate this issue, users should upgrade to version 3.4.2.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.5high · scored by CNA · CWE-653
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Amazon aws-load-balancer-controller
- < 3.4.2
Fixed in 3.4.2
Mitigation
Upgrade aws-load-balancer-controller to 3.4.2 or later.
References
- Release notes github.com/kubernetes-sigs/aws-load-balancer-c…
- Vendor advisory aws.amazon.com/security/security-bulletins/2026-05…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.