Bug 2507526 (CVE-2026-66781)

Summary:	CVE-2026-66781 submariner-operator: pprof debug endpoint enabled by default on 0.0.0.0:8082 without authentication
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security <prodsec-ir-bot>
Status:	NEW ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	gparvin, rhaigner, security-response-team
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in the Submariner operator. The Submariner Custom Resource (CR), used for configuring network connectivity, stores the IPsec pre-shared key (PSK) in an unencrypted format. This key, which is critical for securing communication between Kubernetes clusters, can be accessed by unauthorized parties. Such access enables an attacker to passively decrypt network traffic flowing between any two clusters in the mesh, resulting in sensitive information disclosure.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-07-27 15:44:02 UTC

The Submariner CR exposes a string field for the IPsec pre-shared key. Custom Resources are stored unencrypted in etcd by default (only v1/Secret is encrypted by the OCP KMS provider), are returned by kubectl get submariner -o yaml to anyone with get on the namespaced CR, and are commonly captured in GitOps repos / must-gather bundles. The PSK is identical across all clusters in the mesh, so disclosure on one spoke enables passive decryption of traffic between any two spokes.

Source: Project Glasswing AI-SAST audit of submariner-io/submariner-operator.
Finding ID: FIND-003
Assurance: execution_proven