Citrix Xen Virtualization Software
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in any Citrix Xen product.
RSS Feeds for Citrix Xen security vulnerabilities
Create a CVE RSS feed including security vulnerabilities found in Citrix Xen products with stack.watch. Just hit watch, then grab your custom RSS feed url.
Products by Citrix Xen Sorted by Most Security Vulnerabilities since 2018
By the Year
In 2026 there have been 49 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, 40 more vulnerabilities have already been reported in 2026 as compared to last year. Last year, the average CVE base score was greater by 1.11
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 49 | 6.80 |
| 2025 | 9 | 7.91 |
| 2024 | 19 | 5.72 |
| 2023 | 14 | 6.75 |
| 2022 | 57 | 6.53 |
| 2021 | 27 | 6.96 |
| 2020 | 44 | 6.56 |
| 2019 | 25 | 0.00 |
| 2018 | 27 | 7.72 |
It may take a day or so for new Citrix Xen vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Citrix Xen Security Vulnerabilities
| CVE | Date | Vulnerability | Products |
|---|---|---|---|
| CVE-2026-102703 | Nov 04, 2026 |
Xen Hypervisor Grant Copy Cache Bypass (CVE2026102703)[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] A common access pattern is a batch of Grant Copy operations acting on adjacent address ranges in the same source or destination page. For performance reasons, Xen caches details internally to reuse already validated data. The conditions on when to re-validate the internal data were not correct in some cases: - Frame numbers and grant references could wrongly be mixed up. This is CVE-2026-102703. - Copying by frame number (rather than grant reference) is permitted only when operating on the caller's own memory. The check to enforce this restriction was misplaced. This is CVE-2026-102704. |
|
| CVE-2026-102704 | Nov 04, 2026 |
Xen Hypervisor Grant Copy Validation Bypass (CVE-2026-102704)[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] A common access pattern is a batch of Grant Copy operations acting on adjacent address ranges in the same source or destination page. For performance reasons, Xen caches details internally to reuse already validated data. The conditions on when to re-validate the internal data were not correct in some cases: - Frame numbers and grant references could wrongly be mixed up. This is CVE-2026-102703. - Copying by frame number (rather than grant reference) is permitted only when operating on the caller's own memory. The check to enforce this restriction was misplaced. This is CVE-2026-102704. |
|
| CVE-2026-79611 | Oct 13, 2026 |
Xen Hypervisor VMX VMEntry Failure (CVE-2026-79611)For XSA-308 logic was introduced, as VMX VMEntry checks do not like the exact combination of state which occurs when #DB in intercepted, Single Stepping is active, and blocked by STI/MovSS is active, despite this being a legitimate state to be in. The resulting VMEntry failure is fatal to the guest. Sadly there is another special sub-case of the above, with branch tracing enabled. In that case the prior adjustment would still cause a VMentry failure, as before fatal to the guest. |
|
| CVE-2026-79610 | Oct 13, 2026 |
Xen Hypervisor Grant Table Race Condition Causing Stale Pointers (XSA-501)XSA-501 was about issues with v1 -> v2 and v2 -> v1 changes racing certain other grant table operations. Sadly a v2 -> v1 -> v2 change has yet another effect which wasn't accounted for: During the first change, status pages would be freed. During the second change they would be allocated again. Hence across the full pair of change the addresses of the status pages may change, rendering stale previously calculated pointers into the status array. |
|
| CVE-2026-79609 | Oct 13, 2026 |
Xen Hypervisor XPTI Page Table Isolation Flaw CVE-2026-79609XPTI (Xen Page Table Isolation) was introduced to mitigate Meltdown (CVE-2017-5754, one aspect of XSA-254). This involves copying 64-bit PV guest page table entries from guest-chosen root page tables to the Xen- chosen one which is in actual use by hardware. To read the guest root page table, the directmap is used. PV guests, however, have a directmap which may not cover all memory; in particular this is the case if any memory extends beyond the 5 TiB (CONFIG_BIGMEM=y: 3.5 TiB) address boundary. |
|
| CVE-2026-79608 | Oct 13, 2026 |
Xen Hypervisor - MSR Inverted Conditional Workaround Rework FailureThe workaround for XSA-433 (Zenbleed, CVE-2023-20593) was later re-worked to better integrate with other manipulations of the same MSR. In this rework an inverted conditional was introduced, resulting in the workaround to not be applied when needed and vice versa. For more details, see: http://xenbits.xen.org/xsa/advisory-433.html |
|
| CVE-2026-79607 | Oct 13, 2026 |
Xenstore Watch State Record Byte Omission CrashDuring Xenstore live update the state record for a Xenstore watch with specified watch depth is written with two bytes missing. This results in an inconsistent state when reading the state back in the new Xenstore, causing a crash of Xenstore or wrong Xenstore data. |
|
| CVE-2026-79603 | Sep 08, 2026 |
Xen Hypervisor TLB Flush Race Exposes PV Guest Memory Modificationx86 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. |
|
| CVE-2026-79602 | Sep 08, 2026 |
Xen Hypervisor PCI BAR I/O Port BUG Trigger VulnerabilityA guest with a PCI device assigned that has at least a BAR on the IO port space can trigger a BUG() in Xen. |
|
| CVE-2026-62437 | Sep 08, 2026 |
Xen Hypervisor Guest Termination IRQ Tracking RaceWhen 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. |
|