CVE-2026-77751: Path Traversal Vulnerability Existed
Source GCVE Database
Not known to be exploited · CVSS 8.8 High.
Data as of 20 Nov 2026, 17:35 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 20 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
The described patches introduce strict validation of object-template names to prevent path traversal by restricting allowed characters and replacing invalid names with a safe placeholder. Until an official fix is confirmed, avoid importing or exporting untrusted STIX 2 content containing custom object names. Monitor vendor advisories for updates and apply official patches once available.
Description
A path traversal vulnerability in MISP's handling of object template names during STIX 2 import and MISP-to-STIX 2 export allows crafted object names containing path traversal sequences to escape the intended template directory. This can lead to loading and interpreting unintended definition.json files from other filesystem locations, potentially disclosing local data or altering object metadata. The vulnerability arises because object names from untrusted STIX or MISP content were not properly validated before being used in filesystem paths. Patches introduce strict validation restricting object-template names to safe characters and replace invalid names with a generic placeholder, preventing traversal while preserving source information in comments.