CVE-2026-77751
Received Received - Intake

Path Traversal in MISP STIX 2 Import/Export

Vulnerability report for CVE-2026-77751, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-21

Last updated on: 2026-08-21

Assigner: CIRCL

Description

A path traversal vulnerability existed in the handling of MISP object template names during STIX 2 import and MISP-to-STIX 2 export. MISP object names are passed to PyMISP's object-template resolution mechanism, which constructs a filesystem path by joining the configured MISP object-template directory, the object name, and definition.json. An object name originating from untrusted STIX or MISP content was not sufficiently restricted before being used in this filesystem path. An attacker able to supply a crafted object name containing path separators or traversal sequences such as ../ could therefore cause template resolution to escape the expected template directory and attempt to load a definition.json file from another location accessible to the process. During STIX 2 import, an attacker-controlled x_misp_name from a custom STIX object could directly reach this template-resolution mechanism. The issue could also become persistent. A malicious object name stored in a MISP event could later be processed again during STIX 2 export. Consequently, content originally introduced in one security context could trigger filesystem access later when the event is exported by a process operating with different or greater privileges. If a suitable definition.json file exists outside the intended template directory, its contents may be interpreted as a MISP object template and fields from that file copied into the converted object. This can result in unintended disclosure of locally accessible data represented by the template file and modification of the resulting object's metadata or semantics. The patches introduce strict validation of object-template names. Valid names are restricted to a single path component containing letters, digits, hyphens, or underscores. Names that do not meet these requirements are replaced with the generic unknown-template name before reaching PyMISP template resolution. The original rejected name is preserved in the object's comment and a warning is generated, preventing traversal while retaining the source information.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-21
Last Modified
2026-08-21
Generated
2026-08-21
AI Q&A
2026-08-21
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
misp misp *
pymisp pymisp *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a path traversal vulnerability in MISP's handling of object template names during STIX 2 import and export. Attackers can craft object names with path separators like ../ to escape the intended template directory and access arbitrary files such as definition.json. This allows them to inject malicious content or disclose sensitive local data.

Detection Guidance

To detect this vulnerability, monitor filesystem access patterns in MISP-related processes during STIX import/export operations. Check for unexpected reads of definition.json files outside the configured template directory. Review logs for warnings about invalid object template names or path traversal attempts in MISP event processing.

Impact Analysis

An attacker could read sensitive files on your system or inject malicious data into MISP objects. This could lead to unauthorized data access, modification of object metadata, or persistent compromise if malicious content is later processed with higher privileges during export.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating GDPR's data protection principles or HIPAA's security requirements for protecting sensitive health information. It may result in data breaches requiring regulatory notifications.

Mitigation Strategies
  • Apply the latest patches from the MISP STIX2 repository commits a8b6808d and a0f54070 to sanitize object template names.
  • Update PyMISP to the patched version that includes the _sanitise_template_name function to block path traversal sequences.
  • Review MISP events for malicious object names containing path separators or unusual characters and remove them.
  • Monitor MISP logs for warnings about invalid template names or filesystem access outside the template directory.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-77751. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart