Is CVE-2026-62429 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-62429 being exploited in the wild.

How severe is CVE-2026-62429?

Informational severity, with a CVSS score of 0, published 28 July 2026.

Which products and versions are affected?

Xen Project Xen 4.5 through 4.21.x.

Is there a fix for CVE-2026-62429?

A patch was published on 2026-07-28. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-62429 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-62429?

Check whether you run Xen Project Xen at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-62429: Xen vNUMA race condition during domain destruction

CVE-2026-62429 · Severity: info · CVSS 0 · Published 2026-07-28

A vulnerability in the Xen virtualization platform could allow a compromised or restricted guest management component to gain unauthorized control over the entire physical host. The issue occurs when the system fails to properly synchronize the cleanup of memory configuration data (vNUMA) while a virtual machine is being shut down. An attacker who has already gained control of a guest's device model could exploit this race condition to crash the host, leak sensitive information, or escalate their privileges to take over the entire server.

Technologies: Xen Project Xen. Vendors: Xen Project.

Quick answers

Is CVE-2026-62429 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-62429 being exploited in the wild.
How severe is CVE-2026-62429?: Informational severity, with a CVSS score of 0, published 28 July 2026.
Which products and versions are affected?: Xen Project Xen 4.5 through 4.21.x.
Is there a fix for CVE-2026-62429?: A patch was published on 2026-07-28. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-62429 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-62429?: Check whether you run Xen Project Xen at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A race condition exists in Xen versions 4.5 and later where vNUMA configuration data remains accessible after domain destruction has commenced. The cleanup process for this configuration information is not properly synchronized with its retrieval by the device model controlling the guest. An attacker controlling a device model (running in a stub domain or de-privileged in Dom0) can exploit this lack of synchronization. Successful exploitation can result in a host-wide Denial of Service (DoS), information disclosure, or privilege escalation from a de-privileged device model to host-level privileges. The vulnerability specifically affects x86 HVM guests with vNUMA enabled. Patches are available for stable branches including 4.18.x, 4.21.x, and the unstable branch.

Affected products

Xen Project Xen 4.5 through 4.21.x

Timeline

2026-07-28: disclosed
2026-07-28: advisory
2026-07-28: patched

References

https://xenbits.xenproject.org/xsa/advisory-502.html

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.