Citrix Xen Virtualization Software

By the Year

In 2026 there have been 42 vulnerabilities in Citrix Xen with an average score of 6.8 out of ten. Last year, in 2025 Citrix Xen had 9 security vulnerabilities published. That is, 33 more vulnerabilities have already been reported in 2026 as compared to last year. Last year, the average CVE base score was greater by 1.10

Recent Citrix Xen Security Vulnerabilities

CVE	Date	Vulnerability	Products
CVE-2026-79603	Sep 08, 2026	Xen Hypervisor TLB Flush Race Exposes PV Guest Memory Modification x86 PV guests can free memory pages while still keeping a stale TLB entry pointing to them. A TLB flush is only issued by Xen (if needed) when the page is re-used. Since it's possible for the page to be scrubbed ahead of the TLB flush, there's a window where a PV guest can modify an already scrubbed page.	Xen
CVE-2026-79602	Sep 08, 2026	Xen Hypervisor PCI BAR I/O Port BUG Trigger Vulnerability A guest with a PCI device assigned that has at least a BAR on the IO port space can trigger a BUG() in Xen.	Xen
CVE-2026-62437	Sep 08, 2026	Xen Hypervisor Guest Termination IRQ Tracking Race When guests are terminated, various pieces of cleanup need carrying out. The cleaning up of PCI devices which were assigned to guests, and the associated removal of tracking structures for IRQs used by the devices occurs relatively early in the process. Unfortunately after that point the guest about to be terminated could cause its device model (DM) to re-establish such tracking structures, by having it bind one or more IRQs anew. While some of those tracking structures would still be cleaned up later on, at least one would not be.	Xen
CVE-2026-62434	Jul 28, 2026	Xen PoD Guest Reclaimer Causes Memory Management Corruption A guest started with Populated on Demand enabled (PoD) can attempt to reclaim pages which aren't regular guest RAM. This can cause corruption of memory management state in Xen.	Xen
CVE-2026-62433	Jul 28, 2026	Xen Hypervisor Unchecked Buffer Count in DM_OP leads to stack corruption Parts of the DM_OP handling code assumes the caller has provided the required number of buffers for the given operation without any checking being done. As a result, certain operations might access stack rubble as structures are possibly uninitialized.	Xen
CVE-2026-62432	Jul 28, 2026	XEN Hypervisor Null Pointer Deref via EVTCHNOP_expand_array Race The EVTCHNOP_expand_array hypercall checks for whether FIFO event channels are enabled, but without holding the correct lock. It can race with EVTCHNOP_reset, resulting in dereferencing a NULL pointer.	Xen
CVE-2026-62431	Jul 28, 2026	Xen: Div-by-Zero in Viridian STIMER Handler Causing #DE Fault The logic to handle periodic Viridian STIMERs performs a division with an unchecked user-controlled divisor value, that can be set to zero to cause a #DE fault.	Xen
CVE-2026-62430	Jul 28, 2026	Xen Hypervisor OOB Read via CMOS Index Race Accesses to the CMOS memory contents are done using an indirect IO port pair. Therefore Xen needs to cache the guest chosen index, and one of the usages of the index didn't take the necessary locking to avoid concurrent changes. As a result, a guest could change the index after it being checked, causing a subsequent out-of-bound read access to the contents of an array.	Xen
CVE-2026-62429	Jul 28, 2026	Xen vNUMA Config Leak During Guest Destruction Accessing the vNUMA configuration data of a guest is still possible when domain destruction has already started. The cleaning up of that configuration information is not synchronized with its retrieval by a device model controlling the guest.	Xen
CVE-2026-62435	Jul 28, 2026	Xen Grant Table V1/V2 Switch CVE-2026-62435: Locked State Assumption [This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] With the introduction of Grant Table v2 came the requirement to be able to switch between versions. Switching from v1 to v2 reduces the number of valid grant references, as a bigger shared entry structure is then needed while the shared table doesn't change size. Switching from v2 back to v1 the status frames, which are separate in v2, go away. Code holding, but intermediately dropping and then re-acquiring the grant table lock, sometimes wrongly assumes that said properties wouldn't change across the window in time where the lock is not being held. The v1 -> v2 issue is CVE-2026-62435. The v2 -> v1 issue is CVE-2026-62436.	Xen