The vulnerability arises from KubeVirt's network annotation generator writing the supplied networkName value verbatim into the launcher pod's v1.multus-cni.io/default-network annotation without enforcing DNS-1123 format validation, JSON detection, or special character rejection. The only check rejects empty strings. When the ExternalNetResourceInjection Beta feature gate is enabled (off by default and limited to cluster-admins), the usual NetworkAttachmentDefinition (NAD) lookup that would catch malformed names is bypassed. This allows a tenant with kubevirt.io:edit permissions to inject a JSON-formatted NetworkSelectionElement array specifying arbitrary namespaces, NAD names, static IPs, and MAC addresses. Multus on the node parses this JSON and attaches the launcher pod to the specified network attachment in any namespace, enabling cross-namespace network access and IP/MAC impersonation on network segments normally segregated from tenant workloads. This flaw affects KubeVirt starting from version 1.8.0, first shipped in OpenShift Virtualization 4.21. No official patch or remediation level is stated in the advisory, and no known exploits are reported in the wild.

This vulnerability allows a tenant with kubevirt.io:edit permissions to bypass network segmentation by injecting arbitrary network attachment definitions across namespaces. This can lead to unauthorized cross-namespace network access and IP/MAC address impersonation on network segments that should be isolated. The impact includes limited confidentiality and integrity loss of network communications but does not affect availability. The CVSS 3.1 base score is 4.9 (medium severity) reflecting network attack vector, high attack complexity, low privileges required, no user interaction, scope change, and partial confidentiality and integrity impact.

Patch status is not yet confirmed — check the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-13434 for current remediation guidance. The ExternalNetResourceInjection Beta feature gate is off by default and limited to cluster-admins; disabling or not enabling this feature gate reduces exposure. Restrict kubevirt.io:edit permissions carefully to trusted tenants only. Monitor Red Hat advisories for any official fixes or updates addressing this vulnerability.