{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-62430 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-62430 is a high-severity vulnerability in Xen, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-62430 and fix it if it is affected.\n\nWhat it is: CVE-2026-62430 is a high-severity vulnerability in Xen, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-62430 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-62430/ (Markdown: https://insights.sbomify.com/CVE-2026-62430/index.md)","id":"CVE-2026-62430","markdown":"https://insights.sbomify.com/CVE-2026-62430/index.md","name":"CVE-2026-62430","record":{"aliases":["ALPINE-CVE-2026-62430","DEBIAN-CVE-2026-62430","GHSA-w4qm-qcx6-wmw8","UBUNTU-CVE-2026-62430"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Xen hypervisor","requires_auth":"none","summary":"A race condition in Xen's vRTC emulation allows a guest to trigger an out-of-bounds read, potentially disclosing host memory contents.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"XEN","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"Accesses to the CMOS memory contents are done using an indirect IO port\npair.  Therefore Xen needs to cache the guest chosen index, and one of\nthe usages of the index didn't take the necessary locking to avoid\nconcurrent changes.  As a result, a guest could change the index after\nit being checked, causing a subsequent out-of-bound read access to the\ncontents of an 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":"x86: Out-of-bounds read in vRTC emulation","id":"CVE-2026-62430","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":"Viridian STIMER division by zero","id":"CVE-2026-62431"},"packages":[],"prev":{"headline":"vNUMA domain cleanup may race other operations","id":"CVE-2026-62429"},"products":["Xen"],"published":"2026-07-28","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["Xen"]},"summary":"A race condition in Xen's vRTC emulation allows a guest to trigger an out-of-bounds read, potentially disclosing host memory contents.","url":"https://insights.sbomify.com/CVE-2026-62430/"}