CVE-2026-115396 — Ghidra 10.3 before 12.2 Denial of Service via Compressed Theme Archive
Ghidra 10.3 before 12.2 contains an improper handling of highly compressed data vulnerability in ThemeReader.processIconFile() that fails to limit decompressed size or compression ratio. Attackers can persuade a user to import a crafted theme ZIP whose icon entries expand to fill the host filesystem, causing later writes to fail.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Nationalsecurityagency Ghidra, Nsa Ghidra).
- Apply the fixed version or the patch documented under Remediation.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Nationalsecurityagency | Ghidra | ≥ 10.3 and < 12.2 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Nsa | Ghidra | ≥ 10.3 and < 12.2 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.8 | CVSS 4.0 | Medium | — | — | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 6.8 | CVSS 4.0 | Medium | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 5.5 | CVSS 3.1 | Medium | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H (score shown at the top: disclosure@vulncheck.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 23, 2026 → Oct 28, 2026 · 6 reading(s) · max 0.12%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · nsa/ghidra
- Source status changed · Awaiting Analysis → Analyzed
- SSVC assessment updated
- Source status changed · Received → Awaiting Analysis
- Affected products added · nationalsecurityagency/ghidra
- Record published
- CVSS changed · 5.5
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 22, 2026 – Oct 23, 2026
- 1× Official description updated · Oct 22, 2026 – Oct 22, 2026
References
7 on the record
- github.com/NationalSecurityAgency/ghidra/security/advisories/GHSA-6mj8-x8x9-7gxq
- github.com/NationalSecurityAgency/ghidra/commit/2c2bc5be182d655c9df418ac35b9782f
- www.vulncheck.com/advisories/ghidra-10.3-before-12.2-denial-of-service-via-compressed-t
- nvd.nist.gov/vuln/detail/CVE-2026-115396
- github.com/NationalSecurityAgency/ghidra/releases/tag/Ghidra_12.2_build
- github.com/advisories/GHSA-fr5c-6rcj-3fw2
- github.com/NationalSecurityAgency/ghidra
Elsewhere on this site
Related CVEs (same products)
- Low CVE-2026-116012 Ghidra before 12.2 Integer Truncation in PackedDecode::skipAttribute Decompiler Parser 5d
- Medium CVE-2026-115398 Ghidra before 12.2 Denial of Service via TAR and ZIP File System Mount 7d
- Medium CVE-2026-115503 Ghidra before 12.2 Denial of Service via Compressed Extension Archive 7d
- Medium CVE-2026-115397 Ghidra before 12.2 Denial of Service via Extension Archive Install 7d
- Medium CVE-2026-115394 Ghidra through 12.2 Denial of Service via BinaryField Memory Allocation 7d
- Medium CVE-2026-115395 Ghidra 10.3 before 12.2 Denial of Service via ThemeReader.readZipTheme() 7d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-115396 is "Ghidra 10.3 before 12.2 Denial of Service via Compressed Theme Archive", rated Medium. It affects Ghidra (Nationalsecurityagency); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.12% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.