CVE-2026-77751: misp-stix · Path Traversal
Affects misp-stixSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 19 Nov 2026, 20:25 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mispmisp-stix | Affected
| Fixed in– |
GitHubmisp-stixpkg:github/misp-stixOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Patches are available that introduce strict validation of object-template names, restricting them to safe characters and replacing invalid names with a generic placeholder before template resolution. Users should upgrade to versions later than 2026.7.8 where these fixes are applied. Since this is not a cloud service, remediation requires applying the official patch. No indication exists that no action is required or that the issue is already mitigated without patching. Check the vendor advisory for the latest patch details and apply updates promptly.
Description
CVE-2026-77751 is a path traversal vulnerability in misp-stix affecting the handling of MISP object template names during STIX 2 import and export. The vulnerability allows crafted object names containing path traversal sequences to escape the intended template directory and load arbitrary definition.json files accessible to the process. This can lead to unintended disclosure of local data and modification of object metadata. The issue is mitigated by patches that enforce strict validation of object-template names, restricting them to safe characters and replacing invalid names with a generic placeholder.