CVE-2026-77710
MediumCVSS 6.9Exploitation Probability (EPSS)
Low risk21th percentile - higher than 21% of all known CVEs
Summary
A vulnerability in misp-stix allows an attacker to supply a crafted STIX document that can influence security-sensitive MISP attribute metadata during import. The parser selection was based on untrusted indicators (tool labels or document title), enabling spoofing of MISP-origin content. Additionally, attributes from x-misp-object were copied without restrictions, allowing injection of unexpected fields.
Risk Assessment
Organizations importing STIX documents may inadvertently share information contrary to policy (e.g., overly broad distribution) or process data with falsified tags, affecting automation and downstream processing. An attacker can manipulate classification and metadata, leading to confidentiality or integrity breaches.
Recommendation
Immediately update misp-stix to a patched version that introduces an explicit classification parameter and restricts allowed attribute fields (allow-list). Until updated, suspend STIX imports from untrusted sources or enforce manual specification of document origin.
Other vulnerabilities in misp-stix
See all- CVE-2026-77761Medium
A vulnerability in the misp-stix library stems from incomplete clearing of parser state between STIX document conversions. Reusing the same parser instance can cause data from a previously processed document (e.g., galaxies, DNS records, titles, timestamps) to be incorporated into the MISP event generated from a subsequent document. The issue affects both STIX 1 and STIX 2 parsers.
- CVE-2026-77755High
A denial-of-service vulnerability was identified in misp-stix when processing attacker-controlled STIX 1 or STIX 2 documents. The import code used sys.exit() to handle errors, causing unexpected process termination, and did not limit input size, leading to excessive memory and CPU consumption.
Original NVD description (English source)
A vulnerability in misp-stix could allow a crafted STIX document to influence security-sensitive MISP attribute metadata during import. The STIX import logic automatically selected between the internal MISP parser and the external STIX parser based on metadata contained in the STIX document itself. For STIX2, the presence of MISP-specific tool labels could cause a document to be classified as originating from MISP; similarly, STIX1 relied on the document title. These classification indicators are fully controlled by the STIX producer and therefore cannot constitute a trusted indication of the document's origin. The accompanying fix explicitly notes that the parser choice was previously based solely on labels or header titles that any producer could write, and introduces an explicit classification parameter allowing callers to override this detection. When STIX2 content was handled as an internal MISP export, attributes contained in an x-misp-object were converted by copying the complete x_misp_attributes dictionary and passing it directly to misp_object.add_attribute(). Consequently, a crafted STIX bundle could supply fields that were not part of the expected STIX-to-MISP round-trip format, including security-sensitive properties such as distribution, sharing_group_id, tags, or other MISP attribute fields. An attacker able to provide a STIX document for import could therefore spoof the markers used to identify MISP-generated content and inject additional attribute properties. This could alter the distribution, sharing restrictions, classification, or semantic metadata of imported attributes, potentially causing information to be shared contrary to the importing organization's policy or influencing downstream processing and automation based on attacker-controlled tags or metadata. The vulnerability results from dynamically assigning externally supplied object properties without restricting them to an expected set of attributes, matching CWE-915. MITRE specifically describes this weakness as accepting externally influenced fields without controlling which object attributes may be modified and recommends an allow-list, which is the approach implemented by the patch. The parser-selection issue additionally corresponds to CWE-807, because an untrusted value was used to make a security-relevant trust/classification decision. The attack is also consistent with CAPEC-153 (Input Data Manipulation), in which an attacker controls the structure or flags of supplied data so that the target selects a different processing path or interprets the content differently than intended.