{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-81881 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-81881 is a low-severity memory corruption 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-81881 and fix it if it is affected.\n\nWhat it is: CVE-2026-81881 is a low-severity memory corruption 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: There is no known exploitation of CVE-2026-81881 in the wild and no public exploit code.\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-81881/ (Markdown: https://insights.sbomify.com/CVE-2026-81881/index.md)","id":"CVE-2026-81881","markdown":"https://insights.sbomify.com/CVE-2026-81881/index.md","name":"CVE-2026-81881","record":{"aliases":["GHSA-q4w7-225g-64j9","UBUNTU-CVE-2026-81881"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"radare2 reverse engineering tool","requires_auth":"none","summary":"An attacker can cause a denial of service in radare2 by providing a crafted Mach-O file that triggers a heap out-of-bounds read in the Swift metadata parser.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"radare2","vendor":"radare"}],"cvss":{"score":3.3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-191","name":"Integer Underflow (Wrap or Wraparound)"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"radare2 is a UNIX-like reverse engineering framework and command-line toolset. Prior to 6.2.0, radare2's Mach-O Swift field-metadata parser was vulnerable because a relative Swift field pointer could be lower than the field-metadata section base, making subtraction produce a negative logical index. The vulnerability is triggered by parsing Swift type and class metadata from a crafted Mach-O file. The derived index was used to read four bytes immediately before the allocated field-metadata buffer. This can cause incorrect metadata processing or process termination; no attacker-observable memory disclosure has 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":"none_known"},"has_fix":true,"headline":"radare2: Heap out-of-bounds read in radare2 Mach-O Swift metadata parser","id":"CVE-2026-81881","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"radare:radare2","products":["radare:radare2"],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"radare2: Missing string termination causes heap out-of-bounds read in radare2 bplist parser","id":"CVE-2026-81882"},"packages":[],"prev":{"headline":"radare2: Uncontrolled resource consumption in radare2 PEF loader","id":"CVE-2026-81880"},"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["radareorg"]},"summary":"An attacker can cause a denial of service in radare2 by providing a crafted Mach-O file that triggers a heap out-of-bounds read in the Swift metadata parser.","url":"https://insights.sbomify.com/CVE-2026-81881/"}