// Security Advisory Triage

AWS Load Balancer Controller allows cross-namespace traffic interception via route priority bug

AWS security bulletins · published 2026-10-02 20:03 UTC
ACTION NEEDED VERIFY_EXPOSURE SECURITYAPI
WHAT CHANGEDCVE-2026-15738 disclosed on 14 July 2026. AWS Load Balancer Controller v3.4.1 and later versions incorrectly order ALB listener rules when HTTPRoute and GRPCRoute attach to the same HTTPS listener with the same hostname. HTTPRoute rules always receive lower priority numbers (evaluated first) than GRPCRoute rules, regardless of specificity. A namespace-scoped user with HTTPRoute creation permission can create a catch-all HTTPRoute that intercepts traffic intended for a more-specific GRPCRoute in another namespace.
WHY IT MATTERSIn multi-tenant clusters using shared Gateways, a user with namespace-scoped permissions can intercept traffic destined for services in other namespaces. This breaks namespace isolation and enables privilege escalation — a tenant can read or modify another tenant's traffic without cluster-admin access.
WHAT TO DOCheck if you run AWS Load Balancer Controller v3.4.1 or later with Gateway API enabled and shared Gateways across namespaces. If yes, audit HTTPRoute and GRPCRoute configurations for overlapping hostnames on the same listener, and restrict HTTPRoute creation permissions in untrusted namespaces until patched.
Model-reported confidence 95% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## CVE-2026-15738 - Issue with AWS Load Balancer Controller Cross-Namespace Traffic Interception via HTTPRoute/GRPCRoute Priority Ordering
+https://aws.amazon.com/security/security-bulletins/rss/2026-055-aws/
+Wed, 09 Sep 2026 21:30:11 +0000
+
+Bulletin ID: 2026-055-AWS
+
+Scope: AWS
+
+Content Type: Important (requires attention)
+
+Publication Date: 07/14/2026 13:30 PM PDT
+Description:
+The AWS Load Balancer Controller is an open-source Kubernetes controller that manages AWS Elastic Load Balancing resources for Kubernetes clusters. We identified CVE-2026-15738, an incorrect rule precedence ordering issue in the Gateway API listener rule generation logic. When both an HTTPRoute and a GRPCRoute are attached to the same Application Load Balancer (ALB) HTTPS listener with the same hostname, the controller assigns ALB listener rule priorities based on route kind rather than route specificity. This causes all HTTPRoute-derived rules to receive lower ALB priority numbers, evaluated first by the ALB, than GRPCRoute-derived rules, regardless of which route is more specific. A namespace-scoped user with permission to create HTTPRoute objects in a namespace admitted by a shared Gateway can create a catch-all HTTPRoute that intercepts traffic intended for a more-specific GRPCRoute in another namespace.
+Impacted versions: AWS Load Balancer Controller v3.4.1 and any version that includes support for attaching both HTTPRoute and GRPCRoute to the same listener (introduced in PR #4794)
+Please refer to the article below for the most up-to-date and complete information related to this AWS Security Bulletin.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningAWS Load Balancer Controller is core infrastructure software that platform leads run. Cross-namespace traffic interception is a real privilege escalation.
signalsknown vulnerability in widely-deployed infrastructure software · affects Kubernetes control plane component (Load Balancer Controller) · cross-namespace traffic interception capability · affects shared Gateway configurations common in multi-tenant clusters · privilege escalation path: namespace-scoped user can intercept traffic · specific affected versions identified · security bulletin with CVE identifier
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)