# CVE-2026-13434: Missing authorization in Red Hat OpenShift Virtualization 4

> Tenants can inject network annotations to access other namespaces and impersonate IPs when a specific feature gate is enabled.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:H/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:** 26 Jun 2026
- **Updated:** 27 Jun 2026
- **Also known as:** GHSA-9fjc-whw6-cqfc, MINI-fpm5-fhwg-8854, MINI-xffh-2665-387g

## What is CVE-2026-13434?

CVE-2026-13434 is a medium-severity missing authorization vulnerability in Red Hat OpenShift Virtualization 4, published on 26 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in KubeVirt's network annotation generator. When a tenant creates a VirtualMachineInstance with a Multus network configuration, the supplied networkName value is written verbatim into the launcher pod's v1.multus-cni.io/default-network annotation without format validation or sanitization. The only admission check rejects empty strings; no DNS-1123 format validation, JSON detection, or special character rejection is performed. When the ExternalNetResourceInjection Beta feature gate is enabled (off by default, cluster-admin only), the NAD lookup that would otherwise catch malformed names is skipped by design. A tenant with kubevirt.io:edit permissions can inject a JSON-formatted NetworkSelectionElement array specifying an arbitrary namespace, NAD name, static IP address, and MAC address. 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. The ExternalNetResourceInjection feature gate was introduced in KubeVirt v1.8.0 (first shipped in OpenShift Virtualization 4.21).

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Kubevirt Kubevirt, Redhat Openshift Virtualization.

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

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

## Is CVE-2026-13434 being exploited?

There is no known exploitation of CVE-2026-13434 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-13434 and fix it if it is affected.

What it is: CVE-2026-13434 is a medium-severity missing authorization vulnerability in Red Hat OpenShift Virtualization 4, published on 26 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-13434 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-13434/ (Markdown: https://insights.sbomify.com/CVE-2026-13434/index.md)
```

## Sources

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

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