{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-31053 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-31053 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-31053 is a medium-severity use after free vulnerability in n/a, published on 6 Apr 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-31053 and fix it if it is affected.\n\nWhat it is: CVE-2026-31053 is a medium-severity use after free vulnerability in n/a, published on 6 Apr 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-31053 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-2026-31053/ (Markdown: https://insights.sbomify.com/CVE-2026-31053/index.md)","id":"CVE-2026-31053","markdown":"https://insights.sbomify.com/CVE-2026-31053/index.md","name":"CVE-2026-31053","record":{"aliases":["GHSA-h848-fw25-hp2w"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rizin binary parser","requires_auth":"none","summary":"A double free in the LE binary parser allows attackers to cause denial of service via crafted binaries processed by the library.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rizin","vendor":"rizin"}],"cvss":{"score":6.2,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-415","name":"Double Free"}],"description":"A double free vulnerability exists in librz/bin/format/le/le.c in the function le_load_fixup_record(). When processing malformed or circular LE fixup chains, relocation entries may be freed multiple times during error handling. A specially crafted LE binary can trigger heap corruption and cause the application to crash, resulting in a denial-of-service condition. An attacker with a crafted binary could cause a denial of service when the tool is integrated on a service pipeline.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Use after free in n/a","id":"CVE-2026-31053","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2026-31058"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2026-31052"},"products":["n/a"],"published":"2026-04-06","related":[{"cvss_score":9.1,"headline":"rizin before v0.6.3 is vulnerable to Improper Neutralization of Special Elements via meta_set function in librz/analysis/meta.","id":"CVE-2024-31668","kev_date_added":null,"published":"2024-12-17"},{"cvss_score":7.8,"headline":"Rizin vulnerable to Integer Overflow in C++ demangler logic","id":"CVE-2023-40022","kev_date_added":null,"published":"2023-08-24"},{"cvss_score":7.8,"headline":"Memory corruption in rizin","id":"CVE-2021-3674","kev_date_added":null,"published":"2023-03-24"},{"cvss_score":7.8,"headline":"Rizin has stack-based buffer overflow when parsing GDB registers profile files","id":"CVE-2023-27590","kev_date_added":null,"published":"2023-03-14"},{"cvss_score":7.8,"headline":"Out-of-bounds write when parsing DEX files in Rizin","id":"CVE-2022-36039","kev_date_added":null,"published":"2022-09-06"},{"cvss_score":7.8,"headline":"Rizin Out-of-bounds Write vulnerability in pyc/marshal.c","id":"CVE-2022-36040","kev_date_added":null,"published":"2022-09-06"},{"cvss_score":7.8,"headline":"Rizin Out-of-bounds Write vulnerability in Mach-O binary plugin","id":"CVE-2022-36041","kev_date_added":null,"published":"2022-09-06"}],"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-04-06","vendors":["n/a"]},"summary":"A double free in the LE binary parser allows attackers to cause denial of service via crafted binaries processed by the library.","url":"https://insights.sbomify.com/CVE-2026-31053/"}