{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81878 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-81878 is a medium-severity vulnerability in Radare Radare2, published on 22 Sep 2026. 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-2026-81878 and fix it if it is affected.\n\nWhat it is: CVE-2026-81878 is a medium-severity vulnerability in Radare Radare2, published on 22 Sep 2026. 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-2026-81878 exists.\n\nAffected product: Radare Radare2. 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-81878/ (Markdown: https://insights.sbomify.com/CVE-2026-81878/index.md)","id":"CVE-2026-81878","markdown":"https://insights.sbomify.com/CVE-2026-81878/index.md","name":"CVE-2026-81878","record":{"aliases":["GHSA-9phv-v2w8-56j3","UBUNTU-CVE-2026-81878"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"radare2 reverse engineering tool","requires_auth":"none","summary":"An integer overflow in radare2's PYC parser allows heap corruption and potential code execution when processing crafted files.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"radare2","vendor":"radare"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"radare2 is a UNIX-like reverse engineering framework and command-line toolset. Prior to 6.2.0, radare2's CPython bytecode .pyc marshal parser was vulnerable because the CPython marshal readers accepted a 32-bit string length without rejecting values that overflow the size-plus-one allocation. The vulnerability is triggered by opening or inspecting a crafted .pyc file through r2 or rabin2. A length of 0xffffffff wrapped the allocation to zero before the common byte reader wrote attacker-controlled data and fill bytes beyond the heap allocation. This can cause heap memory corruption and denial of service; arbitrary code execution is possible but has not been demonstrated. This issue is fixed in version 6.2.0.","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":"radare2: Integer overflow causes heap out-of-bounds write in radare2 PYC parser","id":"CVE-2026-81878","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"radare:radare2","products":["radare:radare2"],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"radare2: Heap out-of-bounds read in radare2 ELF PN_XNUM handling","id":"CVE-2026-81879"},"packages":[],"prev":{"headline":"HAPI FHIR: SHCParser DEFLATE infinite loop causes denial of service","id":"CVE-2026-81876"},"products":["radare2"],"published":"2026-09-22","related":[{"cvss_score":10,"headline":"Buffer Overflow and Potential Code Execution in Radare2","id":"CVE-2025-1864","kev_date_added":null,"published":"2025-03-03"},{"cvss_score":10,"headline":"Out-of-bounds Write in radare2","id":"CVE-2025-1744","kev_date_added":null,"published":"2025-02-28"},{"cvss_score":10,"headline":"Denial of service in radare2","id":"CVE-2021-32494","kev_date_added":null,"published":"2023-07-07"},{"cvss_score":10,"headline":"Use after free in radare2","id":"CVE-2021-32495","kev_date_added":null,"published":"2023-07-07"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-29646","kev_date_added":null,"published":"2024-12-17"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-46569","kev_date_added":null,"published":"2023-10-28"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-46570","kev_date_added":null,"published":"2023-10-28"}],"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":"2026-09-22","vendors":["radareorg"]},"summary":"An integer overflow in radare2's PYC parser allows heap corruption and potential code execution when processing crafted files.","url":"https://insights.sbomify.com/CVE-2026-81878/"}