CVE-2026-66785: Submariner: submariner: missing validation of remote endpoint subnets and clusterid enables cross-cluster traffic hijack

Published Jul 27, 2026
·
Updated

A flaw was found in Submariner. This vulnerability allows a malicious cluster (spoke) to redirect network traffic from other connected clusters (peer clusters) by publishing a specially crafted network endpoint. The system fails to properly validate the network subnets provided by the malicious cluster, enabling it to declare arbitrary network ranges. Consequently, all network traffic intended for these arbitrary ranges from peer clusters will be rerouted through the attacker's tunnel, potentially leading to unauthorized information disclosure or network disruption.

Other sources

The broker-to-local sync hook shouldSyncRemoteEndpoint only rejects a remote Endpoint if its subnets overlap the local cluster's own subnets. It does not verify that Spec.ClusterID matches the broker SA that created the CR, that Spec.Subnets are within the CIDRs declared in that cluster's Cluster CR, or that Spec.Subnets do not overlap other remote clusters' subnets. The accepted subnets are installed verbatim as WireGuard AllowedIPs and as Libreswan --client rightSubnet. A malicious spoke can publish an Endpoint with subnets covering arbitrary CIDRs (including 10.0.0.0/8 or 0.0.0.0/0), causing all matching traffic from peer clusters to be routed into the attacker's tunnel.

Source: Project Glasswing AI-SAST audit of submariner-io/submariner. Finding ID: FIND-004 Assurance: executionproven

— Red Hat

Affected Software

1 affected component
Submariner Submariner

Event History

Jul 27, 2026
Data Sourced
via Red Hat·03:44 PM
DescriptionSeverityAffected Software
Aug 20, 2026
CVE Published
via MITRE·06:15 PM
Data Sourced
via MITRE·06:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Deployments with connected Submariner clusters are exposed when a malicious spoke cluster can publish a network endpoint that peer clusters consume. Peer clusters may then route traffic for attacker-declared network ranges through the malicious cluster's tunnel.

2

What does an attacker need to exploit it?

The attacker needs control of a connected cluster that can publish a specially crafted network endpoint with arbitrary subnet ranges. The CVSS vector indicates network reachability, low privileges, and no user interaction are required.

3

What is the likely impact on affected peer clusters?

Traffic intended for arbitrary ranges declared by the malicious cluster can be redirected through the attacker's tunnel. This can result in unauthorized information disclosure or network disruption.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203