CVSS 3.1
4.2 mediumCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:LMedium (4.2). EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:LExplain CVE-2026-13218 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-13218?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-13218?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-13218 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-q3jc-42cq-33fj | Go | kubevirt.io/kubevirt | <=1.10.0-rc.0 | no fix published |
| GO-2026-6914 | Go | kubevirt.io/kubevirt | all versions | no fix published |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Azure Linux | 3 | kubevirt | no fix listed | AZL-91463 |
| Azure Linux | 3 | kubevirt-openvmm | no fix listed | AZL-111647 |
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.
This flaw affects OpenShift Virtualization deployments where virtual machines are configured with bridge or other non-masquerade network interfaces. The default network binding mode in OpenShift Virtualization is masquerade, which does not trigger the vulnerable code path — exploitation requires a cluster administrator to have pre-configured a NetworkAttachmentDefinition with bridge-type binding, a condition beyond the attacker's control. Additionally, the attacker must have exec access to the virt-launcher container (not merely VM guest console access). The file content written by the exploit is constrained to valid JSON following the network cache schema — arbitrary byte injection is not possible. On OpenShift Container Platform, SELinux mandatory access controls in enforcing mode restrict the set of host files writable by the virt-handler process, and base OS binaries under /usr/ are protected by RHCOS read-only ostree layers. However, host configuration files under /etc/ and data under /var/ are potentially reachable depending on virt-handler's SELinux context. Red Hat rates this as Moderate impact because exploitation requires non-default network configuration, container-level access beyond standard VM user privileges, and the content constraint significantly limits the attacker's ability to achieve meaningful host compromise.
Ensure virtual machines use the default masquerade network binding mode where possible. Restrict pods/exec access on virt-launcher pods to only trusted administrators. Review and restrict NetworkAttachmentDefinition resources to limit which namespaces can configure bridge-type network interfaces.
| 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-13218.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.