CVE-2026-77751

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.

• CWE-22

• https://github.com/MISP/misp-stix/commit/a0f54070
• https://github.com/MISP/misp-stix/commit/a8b6808d

Published

Aug 21, 2026

Last Modified

Aug 26, 2026

Status

Deferred

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-77701The WCFM Marketplace WordPress plugin before 3.8.2 does not…5.3
• CVE-2026-77704The Booking for Appointments and Events Calendar WordPress …2.7
• CVE-2026-7771IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4 is …5.5
• CVE-2026-77710A vulnerability in misp-stix could allow a crafted STIX docu…6.9
• CVE-2026-7774tarfile.data_filter could be bypassed using crafted link ent…6.9
• CVE-2026-7775IBM Sterling B2B Integrator 6.2.0.0 through 6.2.0.6, 6.2.1.0…4.8
• CVE-2026-77754The Kirki WordPress plugin before 6.0.14 does not perform a…5.3
• CVE-2026-77755A denial-of-service vulnerability was identified in misp-sti…8.7
• CVE-2026-77757The Directorist: AI-Powered Business Directory, Listings & C…5.4
• CVE-2026-77758The Stripe Payment Forms by WP Full Pay WordPress plugin be…5.3
• CVE-2026-77759Authorization Bypass Through User-Controlled Key in the tran…8.7
• CVE-2026-7776Boundary Community Edition and Boundary Enterprise (“Boundar…7.5