{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-45612 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-45612 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-45612 is a medium-severity memory corruption vulnerability in rizinorg rz-libdemangle, published on 16 Jul 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-45612 and fix it if it is affected.\n\nWhat it is: CVE-2026-45612 is a medium-severity memory corruption vulnerability in rizinorg rz-libdemangle, published on 16 Jul 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-45612 in the wild and no public exploit code.\n\nAffected product: rizinorg rz-libdemangle. 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-45612/ (Markdown: https://insights.sbomify.com/CVE-2026-45612/index.md)","id":"CVE-2026-45612","markdown":"https://insights.sbomify.com/CVE-2026-45612/index.md","name":"CVE-2026-45612","record":{"aliases":["GHSA-4p92-mfjf-qvrc"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rizin demangling library","requires_auth":"none","summary":"An out-of-bounds read in the Rust demangler allows attackers to cause crashes or leak memory when processing malformed symbols.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"rz-libdemangle is a Rizin library for demangling symbols. Prior to 6bf56d3, the Rust demangler in src/rust/rust_v0.c can perform an out-of-bounds read when the demangler structure is not yet initialized. This issue is fixed in commit 6bf56d3.","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":"rz-libdemangle: Out of bound read in rust demangler","id":"CVE-2026-45612","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Rizin: Heap-buffer-overflow in OMF parser","id":"CVE-2026-45613"},"packages":[],"prev":{"headline":"Further research determined the issue is not a vulnerability.","id":"CVE-2026-45611"},"products":["rz-libdemangle"],"published":"2026-07-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":"partial"},"state":"PUBLISHED","updated":"2026-07-16","vendors":["rizinorg"]},"summary":"An out-of-bounds read in the Rust demangler allows attackers to cause crashes or leak memory when processing malformed symbols.","url":"https://insights.sbomify.com/CVE-2026-45612/"}