CVE-2026-15738

Cross-namespace traffic interception via incorrect route precedence ordering in AWS Load Balancer Controller

Published Jul 14, 2026 CVSS 4.0 · 5.8 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The AWS Load Balancer Controller generates Gateway API listener rules in incorrect order when processing HTTPRoute resources. As a result, an authenticated user who can craft a malicious HTTPRoute can cause the controller to route gRPC traffic intended for one namespace to another namespace. This allows interception of data, manipulation of traffic, or denial of service for that namespace's services. The weakness corresponds to improper handling of routing precedence, identified as CWE‑653.

Affected Systems

Amazon’s AWS Load Balancer Controller versions prior to 3.4.2 are susceptible. Any deployment using 3.4.1 or earlier with shared Gateways and multiple namespaces is at risk. The vulnerability does not affect the platform itself, only the configuration of HTTPRoute objects in those older releases.

Risk and Exploitability

The CVSS score of 5.8 indicates moderate severity. The EPSS score is reported as < 1 %, implying a very low probability of exploitation under typical conditions. The vulnerability is not in the CISA KEV catalog. The likely attack vector is an authenticated remote user who has permission to create or modify HTTPRoute resources; such a user could craft a route that redirects traffic from another namespace. While the scope is limited to the Kubernetes cluster’s Gateway configuration, the impact on confidentiality, integrity, and availability for the affected namespace can be significant if exploited. Prompt remediation is recommended to eliminate this risk.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the AWS Load Balancer Controller to version 3.4.2 or later
  • Configure RBAC so that only trusted users can create or modify HTTPRoute resources
  • Audit Gateway API listener rules regularly to detect unintended cross‑namespace routing

Generated by OpenCVE AI on July 31, 2026 at 04:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Cross-namespace traffic interception via incorrect route precedence ordering in AWS Load Balancer Controller
First Time appeared Amazon
Amazon aws-load-balancer-controller
Weaknesses CWE-653
CPEs cpe:2.3:a:amazon:aws-load-balancer-controller:*:*:*:*:*:*:*:*
Vendors & Products Amazon
Amazon aws-load-balancer-controller
References
Metrics cvssV3_1

{'score': 8.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H'}

cvssV4_0

{'score': 5.8, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H'}

Weaknesses
  • CWE-653

    Improper Isolation or Compartmentalization

Sources

Status
PUBLISHED
Assigner
AMZN
Published
Updated
Jul 15, 2026, 1:01 PM
Reserved
Jul 14, 2026, 2:02 PM
Status
Awaiting Analysis
Published
Jul 14, 2026, 9:16 PM
Modified
Oct 24, 2026, 9:10 PM