{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-79610 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-79610 is a high-severity vulnerability in Xen, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-79610 and fix it if it is affected.\n\nWhat it is: CVE-2026-79610 is a high-severity vulnerability in Xen, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-79610 in the wild and no public exploit code.\n\nAffected product: Xen. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-79610/ (Markdown: https://insights.sbomify.com/CVE-2026-79610/index.md)","id":"CVE-2026-79610","markdown":"https://insights.sbomify.com/CVE-2026-79610/index.md","name":"CVE-2026-79610","record":{"aliases":["ALPINE-CVE-2026-79610","DEBIAN-CVE-2026-79610","GHSA-mm4r-fcq9-pfr4","UBUNTU-CVE-2026-79610"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Xen hypervisor","requires_auth":"low_privilege","summary":"A race condition in Xen grant table version changes can lead to stale pointers, potentially allowing code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"XEN","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"XSA-501 was about issues with v1 -\u003e v2 and v2 -\u003e v1 changes racing certain\nother grant table operations.  Sadly a v2 -\u003e v1 -\u003e v2 change has yet\nanother effect which wasn't accounted for: During the first change, status\npages would be freed.  During the second change they would be allocated\nagain.  Hence across the full pair of change the addresses of the status\npages may change, rendering stale previously calculated pointers into the\nstatus array.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"grant-table: double version change race","id":"CVE-2026-79610","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"VMX: VMentry failure with branch tracing and blocked states","id":"CVE-2026-79611"},"packages":[],"prev":{"headline":"x86: XPTI may break on huge-memory systems","id":"CVE-2026-79609"},"products":["Xen"],"published":"2026-10-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["Xen"]},"summary":"A race condition in Xen grant table version changes can lead to stale pointers, potentially allowing code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-79610/"}