{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67873 exists.","fix":"Apply the vendor's patch.","what":"CVE-2025-67873 is a medium-severity memory corruption vulnerability in capstone-engine capstone, published on 17 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-67873 and fix it if it is affected.\n\nWhat it is: CVE-2025-67873 is a medium-severity memory corruption vulnerability in capstone-engine capstone, published on 17 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67873 exists.\n\nAffected product: capstone-engine capstone. 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-67873/ (Markdown: https://insights.sbomify.com/CVE-2025-67873/index.md)","id":"CVE-2025-67873","markdown":"https://insights.sbomify.com/CVE-2025-67873/index.md","name":"CVE-2025-67873","record":{"aliases":["AZL-72700","AZL-72818","AZL-74915","BELL-CVE-2025-67873","CLSA-2026-1774374355","CLSA-2026-1774437715","DEBIAN-CVE-2025-67873","GHSA-hj6g-v545-v7jg","UBUNTU-CVE-2025-67873"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Disassembly framework","requires_auth":"low_privilege","summary":"A heap buffer overflow in Capstone allows attackers to execute arbitrary code or cause denial of service via crafted disassembly input.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"capstone","vendor":"capstone-engine"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"Capstone is a disassembly framework. In versions 6.0.0-Alpha5 and prior, Skipdata length is not bounds-checked, so a user-provided skipdata callback can make cs_disasm/cs_disasm_iter memcpy more than 24 bytes into cs_insn.bytes, causing a heap buffer overflow in the disassembly path. Commit cbef767ab33b82166d263895f24084b75b316df3 fixes the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Capstone doesn't check Skipdata length, leading to cs_insn.bytes heap buffer overflow","id":"CVE-2025-67873","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":"ChurchCRM has plaintext password return in response","id":"CVE-2025-67874"},"packages":[],"prev":{"headline":"Not used","id":"CVE-2025-67871"},"products":["capstone"],"published":"2025-12-17","related":[{"cvss_score":8.8,"headline":"Capstone Integer overflow","id":"CVE-2017-6952","kev_date_added":null,"published":"2017-03-16"},{"cvss_score":5.5,"headline":"Capstone SEGV caused by a read memory access","id":"CVE-2016-7151","kev_date_added":null,"published":"2019-05-15"},{"cvss_score":5.1,"headline":"Capstone has a NULL Pointer Dereference with 3DNow! opcodes","id":"CVE-2026-47143","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":4.8,"headline":"Capstone doesn't check vsnprintf return in SStream_concat, allows stack buffer underflow and overflow","id":"CVE-2025-68114","kev_date_added":null,"published":"2025-12-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-18","vendors":["capstone-engine"]},"summary":"A heap buffer overflow in Capstone allows attackers to execute arbitrary code or cause denial of service via crafted disassembly input.","url":"https://insights.sbomify.com/CVE-2025-67873/"}