{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-61553 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-61553 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-61553 is a high-severity memory corruption vulnerability in n/a, published on 16 Oct 2025. 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-2025-61553 and fix it if it is affected.\n\nWhat it is: CVE-2025-61553 is a high-severity memory corruption vulnerability in n/a, published on 16 Oct 2025. 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-2025-61553 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2025-61553/ (Markdown: https://insights.sbomify.com/CVE-2025-61553/index.md)","id":"CVE-2025-61553","markdown":"https://insights.sbomify.com/CVE-2025-61553/index.md","name":"CVE-2025-61553","record":{"aliases":["GHSA-535q-qgjc-rq5r"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"BitVisor hypervisor","requires_auth":"high_privilege","summary":"Local attackers can crash the BitVisor hypervisor or potentially execute code via an out-of-bounds write in VirtIO network emulation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"An out-of-bounds write in VirtIO network device emulation in BitVisor from commit 108df6 (2020-05-20) to commit 480907 (2025-07-06) allows local attackers to cause a denial of service (host hypervisor crash) via a crafted PCI configuration space access. Given it's a heap overflow in a privileged hypervisor context, exploitation may enable arbitrary code execution or guest-to-host privilege escalation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2025-61553","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2025-61554"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-61550"},"products":["n/a"],"published":"2025-10-16","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":"2025-10-17","vendors":["n/a"]},"summary":"Local attackers can crash the BitVisor hypervisor or potentially execute code via an out-of-bounds write in VirtIO network emulation.","url":"https://insights.sbomify.com/CVE-2025-61553/"}