CVSS 3.1
3.8 lowCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:LLow (3.8). EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:LExplain CVE-2026-13322 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-13322?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-13322?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-13322 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| redhat:openshift_virtualization | from 4 through 4.22.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-6f2p-2qg2-qqch | Go | github.com/kubevirt/kubevirt | >=1.1.0-alpha.0 <=1.10.0-rc.0 | no fix published |
| GO-2026-6912 | Go | kubevirt.io/kubevirt | >=1.1.0-alpha.0 | no fix published |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Azure Linux | 3 | kubevirt | no fix listed | AZL-91454 |
| Azure Linux | 3 | kubevirt-openvmm | no fix listed | AZL-111545 |
From the distributions' data via OSV.dev: Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits.
Red Hat rates this Low.
Red Hat has rated this issue as having Low security impact. The vulnerable code runs in virt-handler, a node-level DaemonSet; however, in OpenShift Virtualization, cgroup memory limits ensure the OOM kill is contained to the virt-handler pod and does not affect the node kernel or kubelet. Running VM workloads (QEMU processes) survive independently and continue operating — only management operations (live migration, graceful shutdown, monitoring updates) are temporarily disrupted. An administrator can recover by deleting the offending VirtualMachineInstance, after which virt-handler resumes normal operation on its next restart. The attack surface is limited to VMIs that explicitly configure a downwardMetrics virtio-serial device, which is not part of the default VM configuration. The blast radius is confined to a single node.
The downward metrics virtio-serial device must be explicitly added to a VM's specification to be present. Clusters that do not use this feature are not exposed. To reduce exposure, administrators can restrict the ability to configure downward metrics devices on tenant VMs by using an admission webhook or policy controller such as Gatekeeper/OPA.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift Virtualization 4 | container-native-virtualization/virt-handler | Fix deferred | |
| Red Hat OpenShift Virtualization 4 | container-native-virtualization/virt-handler-rhel9 | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-13322.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).