Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network vector and PR:N reflect feed-injection attack requiring no MISP credentials; no availability impact as only file reads and metadata modification occur.
Primary rating from Vendor (CIRCL).
CVSS VectorVendor: CIRCL
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
Path traversal in the misp-stix Python library allows an attacker who can supply crafted STIX 2 content to escape the configured object-template directory during PyMISP template resolution, reading arbitrary files accessible to the conversion process and copying their contents into converted MISP objects. All MISP deployments performing STIX 2 import or MISP-to-STIX 2 export via misp-stix are affected, with the flaw carrying a CVSS 4.0 score of 8.8. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation during STIX 2 import requires that the attacker can supply a custom STIX object with a crafted x_misp_name value to the target MISP instance - concretely, by controlling or manipulating a STIX threat feed that MISP subscribes to and processes automatically, or by submitting content directly via a STIX import API endpoint if unauthenticated or attacker-authenticated access to that endpoint exists. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N) scoring 8.8 treats this as a network-accessible, low-complexity, unauthenticated flaw with high confidentiality impact. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who controls or compromises a STIX 2 threat feed subscribed to by the target MISP instance crafts a custom STIX object with x_misp_name set to a traversal sequence such as ../../app/config (PyMISP appends definition.json automatically). When MISP processes the feed during STIX 2 import, PyMISP constructs the path misp_objects_path/../../app/config/definition.json, reads the targeted file if it exists, and copies its contents as template fields into the converted MISP event object - exfiltrating data visible to all event subscribers. … |
| Remediation | Update misp-stix to a release incorporating commits a8b6808d and a0f54070 (https://github.com/MISP/misp-stix/commit/a8b6808d, https://github.com/MISP/misp-stix/commit/a0f54070). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, identify all MISP instances with STIX import/export functionality enabled and document their current misp-stix versions. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Denial-of-service in misp-stix allows remote attackers to terminate long-running MISP importer processes or exhaust host
STIX document import in misp-stix through version 2026.7.8 allows an unauthenticated attacker who can supply a crafted S
Parser state isolation failure in misp-stix corrupts MISP event generation when the same parser instance is reused acros
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-63877
GHSA-wwv2-w4mm-82wm