{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-100505 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-100505 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100505 is a medium-severity memory corruption vulnerability in NationalSecurityAgency ghidra, published on 26 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-100505 and fix it if it is affected.\n\nWhat it is: CVE-2026-100505 is a medium-severity memory corruption vulnerability in NationalSecurityAgency ghidra, published on 26 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-100505 in the wild and no public exploit code.\n\nAffected product: NationalSecurityAgency ghidra. 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-100505/ (Markdown: https://insights.sbomify.com/CVE-2026-100505/index.md)","id":"CVE-2026-100505","markdown":"https://insights.sbomify.com/CVE-2026-100505/index.md","name":"CVE-2026-100505","record":{"aliases":["GHSA-4xhp-h6c8-q4h9"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Reverse engineering tool","requires_auth":"none","summary":"Attackers can crash the Ghidra decompiler or leak heap memory by crafting malicious binaries with invalid multi-byte character sequences.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"ghidra","vendor":"nsa"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Ghidra versions 9.2 through 12.1.4 contain a heap out-of-bounds read vulnerability in StringManager::getCodepoint when decoding multi-byte UTF-8, UTF-16, or UTF-32 characters without validating remaining buffer length. Attackers can craft malicious binaries containing strings or constant byte stores that end in multi-byte lead units to trigger out-of-bounds reads that crash the decompiler or leak adjacent heap memory into decompiled output.","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":"Ghidra 9.2 through 12.1.4 Heap Out-of-Bounds Read via StringManager","id":"CVE-2026-100505","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"WordPress WP Spell Check plugin \u003c= 12.1 - PHP Object Injection vulnerability","id":"CVE-2026-100506"},"packages":[],"prev":{"headline":"Ghidra through 12.1.4 Stack-based Buffer Overflow via leftshift128","id":"CVE-2026-100504"},"products":["ghidra"],"published":"2026-09-26","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-22671","kev_date_added":null,"published":"2023-01-06"},{"cvss_score":9.8,"headline":"XML external entity in n/a","id":"CVE-2019-16941","kev_date_added":null,"published":"2019-09-28"},{"cvss_score":9.1,"headline":"XML external entity in n/a","id":"CVE-2019-13625","kev_date_added":null,"published":"2019-07-17"},{"cvss_score":8.8,"headline":"NSA Ghidra Auto-Analysis Annotation Command Execution","id":"CVE-2026-4946","kev_date_added":null,"published":"2026-03-29"},{"cvss_score":8.7,"headline":"Ghidra 11.0 \u003c 12.1 - SQL Injection in PostgreSQL Password Change via Unescaped Username","id":"CVE-2026-49498","kev_date_added":null,"published":"2026-06-10"},{"cvss_score":8.7,"headline":"Ghidra \u003c 12.1 - Authentication Bypass via Null Signature in PKIAuthenticationModule","id":"CVE-2026-52754","kev_date_added":null,"published":"2026-06-10"},{"cvss_score":8.7,"headline":"Ghidra \u003c 12.1 - SQL Injection via Unescaped Filter Values in BSim Search","id":"CVE-2026-52758","kev_date_added":null,"published":"2026-06-10"}],"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-10-05","vendors":["NationalSecurityAgency"]},"summary":"Attackers can crash the Ghidra decompiler or leak heap memory by crafting malicious binaries with invalid multi-byte character sequences.","url":"https://insights.sbomify.com/CVE-2026-100505/"}