CVE-2026-15738
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.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 8.5
- CVSS 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
- EPSS probability
- 0.65%
- CWE
- CWE-653
- Published
- 2026-07-14
- Last modified
- 2026-07-15
Affected products
- Amazon aws-load-balancer-controller
Weakness type
Related vulnerabilities
- CVE-2026-15366 — A control logic defect in a specific built-in webpage of Kids Mode allows users to view local...
- CVE-2026-71325 — Traefik: `allowCrossNamespace=false` bypass via `@kubernetescrd` TraefikService backendRef
- CVE-2026-62246 — Kamaji: TenantControlPlane namespace/name collision binds two tenants to the same SQL datastore schema + DB user, breaking per-tenant isolation
- CVE-2026-65635 — Boruta dynamic client registration allows creation of over-privileged OAuth clients
- CVE-2026-53421 — Apache Syncope: Remote Code Execution via Scripted Connector
- CVE-2026-53405 — Apache Syncope: Remote Code Execution via Flowable BPMN Groovy ScriptTask
- CVE-2026-63071 — Apache Syncope: RCE via Groovy Sandbox bypass
- CVE-2026-41155 — GPU DDK - SharedSecMem mapped into all GPU virtual address spaces