PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-13318 Red Hat CVE debrief

A server-side request forgery (SSRF) flaw was found in KubeVirt's virt-api port-forward handler. When processing a port-forward request to a VirtualMachineInstance (VMI), virt-api reads the target IP from vmi.Status.Interfaces[0].IP and passes it directly to net.Dial() without validation. For VMIs using non-masquerade network bindings (bridge or secondary-only), this IP is reported by the QEMU guest agent running inside the VM and is fully controllable by the VM owner. An attacker with kubevirt.io:edit permissions can create a VM with a modified guest agent that reports an arbitrary IP address, then request port-forward to establish a bidirectional TCP tunnel from virt-api's cluster-internal network position to any routable destination, bypassing NetworkPolicy isolation.

Vendor
Red Hat
Product
Red Hat OpenShift Virtualization 4
CVSS
MEDIUM 6.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-06-26
Original CVE updated
2026-07-06
Advisory published
2026-06-26
Advisory updated
2026-07-06

Who should care

Users of KubeVirt, particularly those with kubevirt.io:edit permissions, should be aware of this SSRF vulnerability. The flaw allows an attacker to bypass NetworkPolicy isolation and establish a bidirectional TCP tunnel from the cluster-internal network to any routable destination.

Technical summary

The KubeVirt virt-api port-forward handler is vulnerable to SSRF. The handler reads the target IP from vmi.Status.Interfaces[0].IP without validation and passes it to net.Dial(). This allows an attacker with kubevirt.io:edit permissions to create a VM with a modified guest agent reporting an arbitrary IP address and then request port-forward to establish a bidirectional TCP tunnel. The vulnerability is particularly concerning for VMIs using non-masquerade network bindings (bridge or secondary-only), as the IP address is fully controllable by the VM owner.

Defensive priority

Medium priority should be given to patching this vulnerability, as it allows for bypassing NetworkPolicy isolation.

Recommended defensive actions

  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Apply the patch to update KubeVirt
  • Restrict kubevirt.io:edit permissions to trusted users

Evidence notes

The CVE record was published on 2026-06-26T00:16:51.277Z and was last modified on 2026-07-06T17:45:33.717Z. The NVD entry is currently Analyzed. Evidence is limited to CVE and NVD information; further verification is recommended. Defensive verification tasks should include reviewing KubeVirt configurations, monitoring for suspicious activities, and validating network policies.

Official resources

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-06-26T00:16:51.277Z and has not been modified since then. The NVD entry is currently Analyzed.