Not analysed yet
We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.1 | High | 4.0 | CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N | CNA (VulnCheck)Used for this record |
| 7.0 | High | 3.1 | CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H | CNA (VulnCheck) |
- CISA KEV Not listed.
- EPSS 0.0017, the 6th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
Sources
References from the CNA
- github.com/NationalSecurityAgency/ghidra/security/advisories/GHSA-pcfh-853f-q3gh
- github.com/NationalSecurityAgency/ghidra/commit/c03a70d
- github.com/NationalSecurityAgency/ghidra
- github.com/sn0x-sharma/CVE-2026-18718
- www.vulncheck.com/advisories/ghidra-swift-demangler-analyzer-arbitrary-code-execution-via-project-state
- sn0xs-organization.gitbook.io/sn0x-order.org/bb-web-hunt/critical/how-i-found-a-0-day-in-ghidra-shared-project-file-became-a-code-execution-vector