Finding and attribution
Incorrect revalidation of cached grant-copy details can mix frame numbers and grant references (CVE-2026-102703), or place the check restricting frame-number copies to caller-owned memory incorrectly (CVE-2026-102704). Xen’s primary advisory says a malicious guest can read and write arbitrary memory belonging to other domains, including Dom0. The two CVEs are separately identified manifestations in one XSA-523 underlying grant-copy cache-validation issue, so this record counts the shared discovery once.
Product: Xen hypervisor grant-copy operation. AI system: Claude (model/version not identified). Team / organization: Anthropic and Xen Project; validated by Ada Logics; independently reported by CodeAnt AI Security Research Team.
CVE identifiers: CVE-2026-102703, CVE-2026-102704.
AI and human contribution (source account): The signed primary Xen advisory explicitly says the issue was discovered by Anthropic using Claude, then validated by Stephan Lipp of Ada Logics; it also notes an independent report by CodeAnt AI Security Research Team.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: XSA-523 was publicly released Nov 3, 2026. The advisory explicitly separates the two CVE manifestations but presents them as one grant-copy validation issue; they are grouped here as one distinct discovery. No exploitation-in-the-wild claim is made.
Remediation status: fix documented. Apply the appropriate attached XSA-523 patches to the relevant Xen stable branch. The advisory lists no known mitigation. Deployment status is not checked.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 3 Nov 2026. AI attribution dated 3 Nov 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Medium · highest recorded score 4.4. Documented technical effects: data disclosure, data modification.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-102703: CVSS 3.1 · 4.4 (Medium) ·
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N. CISA-ADP (ADP; CVE Program record) · checked 16 Nov 2026. - CVE-2026-102704: CVSS 3.1 · 4.4 (Medium) ·
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N. CISA-ADP (ADP; CVE Program record) · checked 16 Nov 2026.
CVE-2026-102703: data disclosure, data modification.
Prerequisites / affected scope: A malicious guest can read and write arbitrary memory belonging to other Xen domains, including Dom0. CVE-2026-102703 and CVE-2026-102704 share this XSA impact statement; apply to both exact CVEs..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
CVE-2026-102704: data disclosure, data modification.
Prerequisites / affected scope: A malicious guest can read and write arbitrary memory belonging to other Xen domains, including Dom0. CVE-2026-102703 and CVE-2026-102704 share this XSA impact statement; apply to both exact CVEs..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: Apply the appropriate attached XSA-523 patches to the relevant Xen stable branch. The advisory lists no known mitigation. Deployment status is not checked.