Xen fixes two critical grant copy flaws found by Anthropic's Claude that expose dom0 memory
Xen advisory XSA-523 fixes two grant copy flaws that let a guest VM read and write other domains' memory, including dom0. Anthropic found them with Claude.
By Emre A.Published
Tech AI LatestThe Xen Project published advisory XSA-523 on 3 November 2026 for two flaws, CVE-2026-102703 and CVE-2026-102704, in grant copy validation. A malicious guest can read and write memory of other domains, including the privileged dom0. Xen 4.6 and later are affected, patches exist for 4.17 to 4.19 and xen-unstable, and there is no workaround. The advisory credits Anthropic, which found the bugs using Claude.
Key facts
- Published: 3 November 2026 (Xen Security Advisory XSA-523)
- CVEs: CVE-2026-102703 and CVE-2026-102704, both in grant copy validation
- Impact: a malicious guest can read and write memory of other domains, including dom0
- Affected: Xen 4.6 and later; Xen 4.5 and earlier are not vulnerable
- Fixes: patches for xen-unstable and Xen 4.17.x to 4.19.x; none for 4.6 to 4.16; no known mitigation
- Credit: Anthropic using Claude, validated by Stephan Lipp of Ada Logics; independently reported by CodeAnt AI
What the Xen advisory says
The Xen Project security team published XSA-523 on 3 November 2026, and the text was reposted to the oss-security mailing list the same day. It covers two vulnerabilities, CVE-2026-102703 and CVE-2026-102704, in how the hypervisor validates grant copy operations. According to the advisory, a malicious guest can read and write arbitrary memory belonging to other domains, including dom0, the privileged control domain that manages the host.
Every Xen release from 4.6 onward is vulnerable; 4.5 and earlier are not. The Xen Project published patches for xen-unstable and for the 4.17.x, 4.18.x and 4.19.x branches. Branches 4.6 to 4.16 are out of security support and get no patch. The advisory lists no workaround or mitigation other than applying the fix, and it reports no exploitation in the wild.
Xen handles security bugs through a pre-disclosure process: members of its pre-disclosure list, mostly cloud providers, hosting companies and distributions, receive the patches under embargo so they can update hosts before the public advisory. That means many large Xen users had already patched when XSA-523 went public, while smaller operators and self-hosted users depend on the public release and on their distribution's package updates. The advisory's own severity wording, read and write access to dom0 memory from an unprivileged guest, is the most serious class of hypervisor bug, because control of dom0 means control of every guest on the host.
How Claude came into it
The advisory credits Anthropic with discovering the issue using Claude. Stephan Lipp of Ada Logics then validated the findings, and the CodeAnt AI Security Research Team reported the same bugs independently, as The Hacker News also reports. CodeAnt published its own write-up on 4 November under the name Xenbleed, saying the flaw had sat in Xen for more than eleven years. In its test, a guest VM located a marker value in dom0 memory and changed it, which shows the reach into the host's control domain rather than only into Xen's own code.
Grant tables are how Xen guests share memory pages with other domains, and grant copy asks the hypervisor to copy data between those pages on a domain's behalf. Backend drivers for network and disk traffic rely on it, which is why a validation error in that path is serious for any host running untrusted guests, such as public clouds and virtual private server providers.
Ada Logics is a security consultancy known for fuzzing and auditing open-source infrastructure projects, so the validation step adds a human check on top of the model's report. That pattern, an AI system producing a candidate bug and a human researcher confirming it before disclosure, is how most AI-found vulnerabilities have reached maintainers this year. The independent report from CodeAnt AI shows that the bug was within reach of more than one team once it was looked for, which is a reason for operators not to delay the patch.
Who has to patch
Downstream projects moved on the same day. Qubes OS, which uses Xen to isolate its security domains, published bulletin QSB-121, saying all supported Qubes releases are affected, and shipped fixed Xen 4.19.6-3 packages that need a restart to take effect. XCP-ng, the open-source Xen platform maintained by Vates, is also affected, and XenServer users should check Citrix's security bulletins for fixed builds. Operators running older Xen trains from 4.6 to 4.16, often in long-lived appliances, have no official fix and need to upgrade to a supported branch.
Not stated in the advisory: how long Claude took to find the bugs, which Claude model was used, and whether the work was part of Anthropic's own red team program. Those details would help other maintainers judge how repeatable the method is.
Why it matters
Xen is one of the oldest and most audited open-source hypervisors, so a pair of decade-old guest-to-host flaws found with an AI model is a clear marker of where vulnerability research is going. It follows Anthropic's report in late October that an internal Claude model found exploit chains in Chrome, Safari, Android, Windows and Linux, and OpenAI's claim this week that its agents validated 948 Linux kernel root flaws in one run. Google had already reported that monthly CVE disclosures doubled in 2026 as AI tools find more serious bugs.
For maintainers, the practical effect is volume: more findings, found faster, in code that human reviewers have read for years. For defenders, XSA-523 is a reminder that patch windows for virtualization stacks still depend on vendors and distributions rebuilding packages. More coverage is in the cybersecurity section.
The Xen case also shows the credit trail working as intended: the advisory names the company, the model family and the human validator, which lets readers judge the finding. Other projects have handled AI-assisted reports less consistently, and some maintainers have complained about low-quality automated submissions. A confirmed, patched, critical bug with clear attribution is the opposite case, and it is likely to make more open-source maintainers accept AI-assisted reports when they come with a working proof and a human reviewer.
What changed
| Before | Xen 4.6 and later carried two undetected grant copy validation flaws that allowed guest to dom0 memory access |
|---|---|
| After | XSA-523 published on 3 November 2026 with patches for xen-unstable and Xen 4.17.x to 4.19.x; no fix for 4.6 to 4.16 |
| Who it affects | Cloud and hosting providers on Xen, Qubes OS users, XCP-ng and XenServer operators |
Questions people ask
- Which Xen versions are affected by XSA-523?
- All Xen releases from 4.6 onward. Xen 4.5 and earlier are not vulnerable, according to the advisory.
- Is there a workaround for XSA-523?
- No. The advisory lists no mitigation other than applying the patches, which are available for xen-unstable and Xen 4.17.x to 4.19.x.
- Who found the Xen grant copy flaws?
- The advisory credits Anthropic, which found them using Claude. Stephan Lipp of Ada Logics validated the findings, and CodeAnt AI reported them independently.
Sources
- XSA-523: Arbitrary read/write via grant copy (Xen Project, 3 Nov 2026)
- Xen Security Advisory 523 (oss-security repost) (Openwall oss-security, 3 Nov 2026)
- QSB-121: Arbitrary read/write via grant copy (XSA-523) (Qubes OS, 3 Nov 2026)
- Xen Hypervisor Flaws Let One Malicious VM Read and Write Any Other VM's Memory (The Hacker News, 4 Nov 2026)
- Xenbleed: a grant copy cache bug that reaches dom0 memory (CodeAnt AI, 4 Nov 2026)
Reference pages
- Anthropic company
Spotted an error? See the corrections policy and tell the editor. Facts in this story come from the sources listed above; vendor claims are attributed.
Comments
Loading comments.





