CVE-2026-77761
Received Received - Intake

State Retention in MISP STIX Parser Leading to Data Contamination

Vulnerability report for CVE-2026-77761, 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 parser state isolation vulnerability in misp-stix could cause data from a previously processed STIX document to be retained and incorporated into the MISP event generated from a subsequent document when the same parser instance is reused. Several STIX 1 and STIX 2 parser components maintained per-document state that was not completely cleared between conversions. In the STIX 2 parser, galaxy and galaxy-cluster information, including custom galaxy clusters, could survive a parser reset and subsequently be associated with objects from another bundle. The STIX 1 parsers were affected by the same underlying state-management issue. Depending on the parser type, retained information could include galaxies, references, passive DNS bookkeeping, package titles, dates, and timestamps. As a result, parsing a second STIX package with an already-used parser could produce a MISP event containing information that was present only in the previously processed package. For example, a generated event could inherit passive DNS records from an earlier document, reference unrelated galaxy information, combine titles from different packages, or use timestamps originating from another conversion. The issue primarily affects applications using the misp-stix API directly and reusing parser instances across independent STIX documents. Normal conversion entry points that instantiate a new parser for each file are not affected by this particular reuse scenario. An attacker able to influence documents processed by such a long-lived parser could potentially cause information from one conversion to contaminate a subsequent MISP event. This can affect the integrity of generated threat intelligence, resulting in incorrect associations, misleading contextual information, or unrelated indicators being attributed to an event. In environments where consecutive documents have different access controls or distribution scopes, the retained state could additionally result in limited disclosure of information from a previously processed document. Successful exploitation depends on the consuming application reusing the same parser instance and on the ordering of processed documents, which increases attack complexity. No direct availability impact or code execution is involved.

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 1 associated CPE
Vendor Product Version / Range
misp misp-stix *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-459 The product does not properly "clean up" and remove temporary or supporting resources after they have been used.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves parser state isolation in misp-stix where data from a previously processed STIX document is retained and incorrectly included in a new MISP event when the same parser instance is reused. This happens because the parser's state, including galaxy clusters, references, and other metadata, is not fully cleared between document conversions.

Detection Guidance

Detecting this vulnerability requires checking if your misp-stix parser reuses instances across documents without proper state reset. Review application logs for parser reuse patterns and inspect code for manual state clearing between STIX document processing.

Impact Analysis

An attacker could manipulate documents processed by a reused parser to contaminate subsequent MISP events with incorrect or unrelated data. This may lead to misleading threat intelligence, wrong associations, or unintended disclosure of sensitive information from prior documents if access controls differ between documents.

Compliance Impact

This vulnerability could violate compliance by causing unintended data leakage between documents with different access controls or distribution scopes. For example, sensitive information from one document might be incorrectly included in another, potentially breaching GDPR or HIPAA requirements for data isolation and confidentiality.

Mitigation Strategies

Update to the patched versions of misp-stix that include state reset fixes. Ensure parser instances are either reused with proper state clearing or instantiate new parsers for each document. Review STIX1 and STIX2 parsers for similar state management issues.

Chat Assistant

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

EPSS Chart