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.