{}

{}

{}

{"bugzilla": {"description": "submariner: submariner: ipsec.conf stanza injection via remote-supplied CableName and Subnets", "id": "2507531", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2507531"}, "csaw": false, "cvss3": {"cvss3_base_score": "9.1", "cvss3_scoring_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H", "status": "draft"}, "cwe": "CWE-94", "details": ["A flaw was found in submariner. In cert-auth mode, the connection configuration is built using free-form strings from the Custom Resource Definition (CRD) without proper validation. A malicious cluster can exploit this by publishing a CableName that includes newlines and ipsec.conf directives. This allows an attacker to inject arbitrary configuration parameters or execute commands through leftupdown hooks, leading to remote code execution as root on the gateway node."], "mitigation": {"lang": "en:us", "value": "If Submariner certificate-based IPsec authentication mode is enabled (`IPSecCertAuthMode: true` in the SubmarinerConfig), administrators can mitigate this flaw by switching to the default pre-shared key (PSK) authentication mode. Set `IPSecCertAuthMode: false` (or remove the field to use its default value) in the SubmarinerConfig CR and redeploy the Submariner gateway pods. PSK mode provides equivalent inter-cluster IPsec tunnel encryption and is not affected by this vulnerability. Note that disabling cert-auth mode means Submariner will no longer integrate with OVN IPsec's certificate infrastructure and will manage its own PSK-based authentication independently."}, "name": "CVE-2026-66786", "public_date": "2026-08-21T16:43:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-66786\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-66786"], "statement": "Red Hat rates this flaw as Moderate severity rather than Important because exploitation requires two non-default configurations that must both be explicitly enabled by an administrator. The vulnerable code path exists only in Submariner's certificate-based IPsec authentication mode, which is disabled by default (`IPSecCertAuthMode` defaults to `false`). This mode is designed specifically for integration with OVN-Kubernetes IPsec, which is itself an optional intra-cluster encryption feature that is also disabled by default. The standard Submariner deployment, including multi-cloud and cross-datacenter configurations managed through Red Hat Advanced Cluster Management, uses pre-shared key (PSK) authentication, which establishes IPsec tunnels through a structurally different code path (`ipsec whack` command-line arguments via Go's `exec.Command`) that is not susceptible to this injection. Additionally, exploitation requires that an attacker has already compromised a managed spoke cluster at the cluster-admin level in order to extract the Submariner broker credentials, and must then bypass all normal Submariner automation to craft and submit a malicious Endpoint resource directly to the broker API, enabling cross-cluster lateral movement to other clusters within the same ManagedClusterSet. Clusters in other ManagedClusterSets have separate broker credentials and are not reachable through this attack.", "threat_severity": "Moderate"}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": null}], "enrichment": {"confidence": 80.0, "confidence_source": "inferred", "scores": [{"score": 80.0, "source": "inferred"}]}, "product": "submariner", "vendor": "submariner"}], "created": "2026-08-22T01:45:04.000078+00:00", "updated": "2026-08-24T21:09:52.852245+00:00", "vendors": ["submariner", "submariner$PRODUCT$submariner"]}