Skip to main content
Mallory
UnratedVulnerability

CVE-2026-102708: Privilege escalation through XAPI message handling in XenServer

Updated 10 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 2 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-102708CWE-863

CVE-2026-102708 is an authorization vulnerability in XAPI message handling that allows an authenticated user with the vm-power-admin role to submit a crafted message body and perform arbitrary symbolic-link or directory creation operations in the host's dom0 environment as root. The vulnerability crosses the intended role-based access control boundary and can enable escalation to the fully privileged pool-admin role. All XAPI versions are affected; affected XenServer products include XenServer 8.4 and XenServer 9.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A lower-privileged VM Power Administrator can perform unauthorized filesystem operations as root in dom0 and potentially escalate to Pool Administrator. The pool-admin role permits root SSH access to hosts, compromising the intended separation between delegated VM administration and fully privileged host administration.

Mitigation

If you can’t patch tonight, do this now.

Until updates are applied, disable RBAC subjects assigned the vm-power-admin role to remove the documented attacker's required privileges. The broader XSA-530 mitigation recommends disabling subjects assigned any of the read-only, vm-operator, vm-admin, vm-power-admin, or pool-operator roles to address the complete vulnerability set.

Remediation

Patch, then assume compromise.

Apply the appropriate XAPI patches supplied with Xen Security Advisory XSA-530. For XenServer 8.4 and XenServer 9, install the latest security updates available through the selected Early Access or Normal update channel, following Citrix advisory CTX697316 and the applicable update documentation. Exact fixed build numbers are not available.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-102708 exploited in the wild?
As of Nov 12, 2026, Mallory has no reports of CVE-2026-102708 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-102708?
As of Nov 12, 2026, Mallory has found no public exploit for CVE-2026-102708.
Is there a patch for CVE-2026-102708?
Apply the appropriate XAPI patches supplied with Xen Security Advisory XSA-530. For XenServer 8.4 and XenServer 9, install the latest security updates available through the selected Early Access or Normal update channel, following Citrix advisory CTX697316 and the applicable update documentation.
Activity feed

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.