{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-79611 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-79611 is a medium-severity denial of service 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-79611 and fix it if it is affected.\n\nWhat it is: CVE-2026-79611 is a medium-severity denial of service 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-79611 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-79611/ (Markdown: https://insights.sbomify.com/CVE-2026-79611/index.md)","id":"CVE-2026-79611","markdown":"https://insights.sbomify.com/CVE-2026-79611/index.md","name":"CVE-2026-79611","record":{"aliases":["ALPINE-CVE-2026-79611","DEBIAN-CVE-2026-79611","GHSA-28w8-qvww-f539","UBUNTU-CVE-2026-79611"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Xen hypervisor","requires_auth":"low_privilege","summary":"A guest VM can cause a fatal VMEntry failure and crash itself by triggering a specific state combination involving branch tracing and blocked states.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"XEN","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"}],"description":"For XSA-308 logic was introduced, as VMX VMEntry checks do not like the\nexact combination of state which occurs when #DB in intercepted, Single\nStepping is active, and blocked by STI/MovSS is active, despite this being\na legitimate state to be in.  The resulting VMEntry failure is fatal to\nthe guest.\n\nSadly there is another special sub-case of the above, with branch tracing\nenabled.  In that case the prior adjustment would still cause a VMentry\nfailure, as before fatal to the guest.","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":"VMX: VMentry failure with branch tracing and blocked states","id":"CVE-2026-79611","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Apache Answer: Disclosure of Comments on Non-Public Content Through Public Profiles","id":"CVE-2026-79613"},"packages":[],"prev":{"headline":"grant-table: double version change race","id":"CVE-2026-79610"},"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":"partial"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["Xen"]},"summary":"A guest VM can cause a fatal VMEntry failure and crash itself by triggering a specific state combination involving branch tracing and blocked states.","url":"https://insights.sbomify.com/CVE-2026-79611/"}