# CVE-2026-116012: Ghidra before 12.2 Integer Truncation in PackedDecode::skipAttribute Decompiler Parser


- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** GHSA-5r3f-xv7p-f23m, GHSA-v423-5vh7-c7jw

## What is CVE-2026-116012?

CVE-2026-116012 is a low-severity vulnerability in NationalSecurityAgency ghidra, published on 24 Oct 2026. 

### Official description

Ghidra before 12.2 contains a numeric truncation vulnerability in PackedDecode::skipAttribute and skipAttributeRemaining in marshal.cc that stores 64-bit string lengths in 32-bit variables. Attackers can supply a crafted packed stream, such as a malicious .sla file, to inject attributes into the decompiler's input or crash the decompiler process.

Weakness: CWE-197 (Numeric Truncation Error)

## Which versions are affected by CVE-2026-116012?


## How do I fix CVE-2026-116012?

No fix has been published for CVE-2026-116012 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116012 being exploited?

There is no known exploitation of CVE-2026-116012 in the wild and no public exploit code.

Public exploit code:

- NSA Ghidra contains a numeric truncation vulnerability in PackedDecode::skipAttribute and skipAttributeRemaining in marshal.cc. (github_poc): https://github.com/D7EAD/CVE-2026-116012

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116012 and fix it if it is affected.

What it is: CVE-2026-116012 is a low-severity vulnerability in NationalSecurityAgency ghidra, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116012 in the wild and no public exploit code.

Affected product: NationalSecurityAgency ghidra. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116012/ (Markdown: https://insights.sbomify.com/CVE-2026-116012/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116012
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116012
- OSV: https://osv.dev/vulnerability/CVE-2026-116012

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116012/
Summaries are generated and may contain mistakes; the official description above is the record.