VulnerabilityPublished 26 Jun 2026Updated 4 Nov 2026

CVE-2026-13318: kubevirt.io/kubevirt · KubeVirt virt-api port-forward handler vulnerable to SSRF via guest-controlled VMI IP address

Affects kubevirt.io/kubevirtSource GCVE Database

Compare

Authoritative record:CVE-2026-13318· Medium 6.4

Not known to be exploited · CVSS 6.4 Medium : upgrade to 1.10.0-rc.0 when convenient.

Data as of 4 Nov 2026, 18:30 UTC

CVSS 3.1 base score

6.4Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 1.10.0-rc.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade kubevirt.io/kubevirt to 1.10.0-rc.0.

Affected software

Product	Affected	Fixed in
Gokubevirt.io/kubevirt	Affected <1.10.0-rc.0	Fixed in 1.10.0-rc.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in KubeVirt version 1.10.0-rc.0 and later; users should upgrade to these versions to remediate the vulnerability. For environments using bridge or secondary-only network bindings, cluster administrators can apply egress NetworkPolicy rules to the openshift-cnv namespace to restrict virt-api's outbound connections to known legitimate destinations such as launcher pod CIDRs and node IPs, blocking SSRF attempts to arbitrary targets. Users not using these network bindings are not affected and require no action.

Description

CVE-2026-13318 is a server-side request forgery (SSRF) vulnerability in KubeVirt's virt-api port-forward handler. The flaw arises because virt-api uses an IP address reported by the QEMU guest agent inside a VirtualMachineInstance (VMI) without validation. For VMIs using non-masquerade network bindings (bridge or secondary-only), this IP is fully controllable by the VM owner. An attacker with kubevirt.io:edit permissions can exploit this to create a VM that reports an arbitrary IP, enabling port-forward requests to establish TCP tunnels to arbitrary internal or external network destinations, bypassing NetworkPolicy isolation. The issue affects versions prior to 1.10.0-rc.0 and has been fixed starting with 1.10.0-rc.0. The vulnerability has a CVSS 3.1 score of 6.4 (medium severity).

Impact

An attacker with kubevirt.io:edit permissions can exploit this SSRF vulnerability to establish bidirectional TCP tunnels from the cluster-internal network position of virt-api to arbitrary routable IP addresses. This bypasses NetworkPolicy isolation, potentially allowing unauthorized access or scanning of internal network resources. The confidentiality and integrity impacts are rated low, and availability is not affected. The vulnerability only affects VMIs using bridge or secondary-only network bindings; default masquerade network bindings are not vulnerable.

Summary

KubeVirt's virt-api port-forward handler reads the target IP address for port-forwarding from vmi.Status.Interfaces[0].IP, which is reported by the QEMU guest agent inside the VM. For VMIs configured with bridge or secondary-only network bindings, this IP is controlled by the VM guest, allowing an attacker with edit permissions to specify arbitrary IP addresses. This leads to a server-side request forgery (SSRF) vulnerability where the virt-api component can be tricked into dialing arbitrary TCP endpoints inside or outside the cluster, bypassing network isolation policies. The vulnerability requires kubevirt.io:edit permissions and affects versions before 1.10.0-rc.0, which contains the fix. Red Hat rates the impact as moderate and recommends applying egress NetworkPolicy restrictions on the openshift-cnv namespace to limit virt-api's outbound connections if bridge or secondary-only network bindings are used.

CWE-918Server-Side Request Forgery (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Implementation · Operation
If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Operation
If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 18:30 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats