CVE-2026-133531: Cluster-network-operator: cluster-network-operator: ipsec signer fails to bind certificate identity to the requesting node
A flaw was found in cluster-network-operator. The network.openshift.io/signer controller validates that a certificate signing request originates from an existing OVN node username but does not bind the requested certificate Subject and DNS SANs to that node. An attacker possessing an accepted OVN node credential and CSR submission permission can request a CA-signed certificate identifying another node chassis. In the reported OVN IPsec scenario, impersonation additionally requires separate control of the victim underlay address to satisfy the configured peer address check; the signer defect does not itself provide this capability. Successful impersonation could compromise the confidentiality and integrity of protected traffic. Cross identity issuance is supported by source review; complete IKE impersonation and traffic interception have not been independently reproduced. The supplied patch and fake client tests were reviewed statically, not applied or executed. Preliminary CVSS v3.1: 5.9 (Medium), CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N. This score assumes successful impersonation allows reading and modifying victim traffic and remains subject to confirmation. Reported by Avinash Duduskar; preferred acknowledgment name is pending confirmation.
Other sources
A flaw was found in cluster-network-operator. The OVN IPsec certificate signer does not verify that the requested certificate Subject and DNS names belong to the requesting node. An attacker with an accepted OVN node credential and permission to submit certificate signing requests could obtain a signed certificate identifying another node. In certificate authenticated OVN IPsec deployments, this could enable peer impersonation when the attacker can also satisfy the configured peer address check, potentially compromising protected traffic.
— MITRE
Affected Software
Event History
Frequently Asked Questions
Who is realistically exposed to this issue?
Exposure requires an attacker to possess an accepted OVN node credential and permission to submit certificate signing requests. The reported impact applies to OVN IPsec deployments where a certificate can be used to impersonate another node chassis.
What additional condition is needed to impersonate a victim node in the reported IPsec scenario?
The attacker must separately control the victim's underlay address so that the configured peer address check succeeds. The signer flaw alone does not provide control of that address.
What could an attacker gain if impersonation succeeds?
Successful impersonation could compromise the confidentiality and integrity of protected traffic, allowing the attacker to read and modify that traffic. Complete IKE impersonation and traffic interception have not been independently reproduced.
How certain is the reported exploitability and remediation status?
Cross-identity certificate issuance is supported by source review. However, the supplied patch and fake-client tests were reviewed statically and were not applied or executed, and end-to-end IKE impersonation has not been independently reproduced.