# CVE-2026-13318: Virt-api-rhel9: kubevirt: kubevirt: ssrf in virt-api port-forward via unvalidated guest-agent-reported ip

> An attacker with edit permissions can exploit unvalidated guest agent IPs in KubeVirt to perform SSRF, bypassing network policies and accessing internal services.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** AZL-91457, GHSA-cgm6-wvp9-4g5h, MINI-fhwq-473v-v2rj, MINI-jjgp-vjmc-h48v

## What is CVE-2026-13318?

CVE-2026-13318 is a medium-severity server-side request forgery vulnerability in Red Hat OpenShift Virtualization 4, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-13318?

It affects 2 products.


Products: Kubevirt Kubevirt, Redhat Openshift Virtualization.

## How do I fix CVE-2026-13318?

No fix has been published for CVE-2026-13318 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13318 being exploited?

There is no known exploitation of CVE-2026-13318 in the wild and no public exploit code.

## Other vulnerabilities in Red Hat OpenShift Virtualization 4

- [CVE-2020-14316](https://insights.sbomify.com/CVE-2020-14316/): Privilege Escalation in kubevirt (critical 9.9)
- [CVE-2022-1798](https://insights.sbomify.com/CVE-2022-1798/): Path Traversal vulnerability in Kubevirt (high 8.7)
- [CVE-2025-64324](https://insights.sbomify.com/CVE-2025-64324/): KubeVirt Vulnerable to Arbitrary Host File Read and Write (high 8.5)
- [CVE-2023-26484](https://insights.sbomify.com/CVE-2023-26484/): On a compromised KubeVirt node, the virt-handler service account can be used to modify all node specs (high 8.2)
- [CVE-2026-13201](https://insights.sbomify.com/CVE-2026-13201/): Path traversal in Red Hat Container Native Virtualization 4.12 (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13318 and fix it if it is affected.

What it is: CVE-2026-13318 is a medium-severity server-side request forgery vulnerability in Red Hat OpenShift Virtualization 4, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-13318 in the wild and no public exploit code.

Affected product: Red Hat OpenShift Virtualization 4. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-13318/ (Markdown: https://insights.sbomify.com/CVE-2026-13318/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13318
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13318
- OSV: https://osv.dev/vulnerability/CVE-2026-13318

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13318/
Summaries are generated and may contain mistakes; the official description above is the record.