CVSS 3.1
6.5 mediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:HMedium (6.5). 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:HExplain CVE-2026-13208 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-13208?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-13208?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-13208 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 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Azure Linux | 3 | kubevirt | no fix listed | AZL-91460 |
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 Moderate.
Red Hat has assessed this issue as Moderate impact for OpenShift Virtualization. In a default deployment, a user with namespace edit permissions can exec into their own virt-launcher pod and exploit the unvalidated VMI identity in the notify server to disrupt co-located VMs belonging to other tenants. The attack is limited to denial of service (forced shutdown/restart of targeted VMs) and does not provide data access or code execution. Exploitation requires: (1) shell access inside a virt-launcher pod on the target node, (2) knowledge of the victim VMI's namespace and name, and (3) the victim VM to be scheduled on the same node. SELinux MCS labels do not mitigate this because the notify pipe socket is a legitimate communication channel accessible to the launcher process. Network policies are irrelevant as this uses local Unix sockets.
Organizations can reduce exposure by: (1) restricting pods/exec permission on virt-launcher pods via admission policies (e.g., Gatekeeper or Kyverno rules denying exec on pods with the kubevirt.io launcher label), (2) using node affinity or dedicated node pools to isolate high-security tenant workloads from untrusted tenants, and (3) monitoring for unexpected VMI state transitions via cluster alerting.
| 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-13208.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.