Skip to main content

misp-stix CVE-2026-77761

| EUVDEUVD-2026-63883 MEDIUM
Incomplete Cleanup (CWE-459)
2026-08-21 CIRCL GHSA-q62h-w723-22p2
6.3
CVSS 4.0 · Vendor: CIRCL
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify pipeline reusing misp-stix parser instance
  2. Delivery
    Submit crafted STIX bundle with attacker-controlled galaxy/DNS/timestamp state
  3. Exploit
    Parser accumulates injected data into instance accumulators
  4. Execution
    Legitimate STIX document parsed by same instance
  5. Persist
    Resulting MISP event inherits prior document artifacts
  6. Impact
    Downstream analysts or automated systems act on contaminated threat intelligence

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Incomplete cleanup
Exploitation Conditions

Exploitation requires two specific, non-default conditions to hold simultaneously: first, the consuming application must reuse the same misp-stix parser instance across two or more independent STIX document conversions - standard conversion entry points that instantiate a new parser per file are explicitly not affected per the CVE description; second, the attacker must be able to influence the content of at least one STIX document processed by that long-lived parser instance before the target document is processed, and must be able to control or predict document processing order. The AT:P (attack precondition present) metric in the CVSS 4.0 vector formally encodes the parser-reuse requirement. Exploitation is strictly bounded to partial integrity contamination and limited disclosure of prior-document metadata; no code execution, privilege escalation, authentication bypass, or availability impact is possible per the description and confirmed by the patch diffs.

Impact

The CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N) scores 6.3, reflecting a network-reachable attack surface bounded by a required attack precondition (AT:P) - specifically, the consuming application must reuse parser instances across unrelated documents, which is explicitly a non-default usage pattern. Impacts are limited to partial confidentiality and integrity of the vulnerable system with no availability or scope change. No EPSS data was provided in the input, and the vulnerability is not listed in CISA KEV. No public proof-of-concept exploit code has been identified. The 'RCE' tag present in the input data is inconsistent with both the CVE description and the patch diffs, which explicitly state 'No direct availability impact or code execution is involved' - this tag should be disregarded as likely mislabeled metadata and does not alter the risk calculus. Real-world risk is low-to-moderate for most environments but operationally significant in threat-intelligence pipelines that process documents from mixed-trust sources with a shared parser instance, where false associations or metadata leakage between events could mislead analysts or violate distribution controls.

Exploit ScenarioDerived

An attacker with the ability to inject a crafted STIX document into a threat-intelligence ingestion pipeline that reuses a misp-stix parser instance submits a bundle containing fabricated galaxy clusters, passive DNS records, or false timestamps targeting a known processing queue. When a legitimate high-priority STIX document is subsequently processed by the same instance, the resulting MISP event inherits the attacker's injected artifacts, causing false threat-actor associations or incorrect indicator attribution to propagate downstream to analysts and automated response systems. No public proof-of-concept exploit code has been identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 21, 2026

Parser state isolation failure in misp-stix corrupts MISP event generation when the same parser instance is reused across independent STIX 1 and STIX 2 document conversions, causing retained artifacts - including galaxy clusters, passive DNS records, package titles, dates, and timestamps - from a prior document to contaminate subsequently generated MISP events. Applications directly consuming the misp-stix API with long-lived parser instances are at risk; the standard entry points that instantiate a fresh parser per file are not affected. No public exploit has been identified at time of analysis, and the CVSS 4.0 AT:P precondition metric confirms exploitation depends on a non-default deployment pattern compounded by attacker influence over document processing order.

RemediationAI

Update misp-stix to a version incorporating commits f08373dd, ad4f0a65, and f6593931 from the MISP GitHub repository (https://github.com/MISP/misp-stix/commit/f08373dd and https://github.com/MISP/misp-stix/commit/f6593931). Because an exact fixed release tag was not confirmed in available data, verify the target version by checking the misp-stix PyPI changelog or MISP project release notes for a version post-dating these commits before upgrading. As an immediate workaround requiring no library change, refactor any application that directly consumes the misp-stix API to instantiate a new parser object for each STIX document conversion rather than reusing the same instance - this fully eliminates the vulnerable reuse path and matches the behavior of the standard non-API entry points. If refactoring is not immediately feasible, implement strict document queue isolation to prevent attacker-influenced STIX documents from being processed consecutively with sensitive documents on the same parser instance; this reduces but does not eliminate integrity risk.

Affected VersionsENISA

misp-stix 0 ≤2026.7.8

Affected Packages

euvd misp_stix no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

misp-stix (CPE: cpe:2.3:a:misp:misp-stix:*:*:*:*:*:*:*:*) is a CIRCL-maintained Python library that converts between STIX 1.x/2.x threat intelligence bundles and MISP event structures. The root cause is CWE-459 (Incomplete Cleanup): three parser classes - ExternalSTIX1toMISPParser, InternalSTIX1toMISPParser, and the base STIX1toMISPParser - initialized per-document state accumulators (self.__dns_objects, self.__dns_ips, self.__dates, self.__timestamps, self.__titles, self.__galaxies, self.__references) inside their constructors rather than inside a dedicated reset method invoked at each conversion entry point. When parse_stix_package or parse_stix_content was called on an already-used instance, these accumulators still held values from prior runs. The STIX 2 parser suffered the same pattern for galaxy and galaxy-cluster data. The upstream fix (commits f08373dd, ad4f0a65, f6593931) introduces a _reset_bundle_state() hook called at every conversion entry point, ensuring each conversion starts from a clean accumulator state whether the parser object is newly instantiated or reused.

Know when Misp gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (CIRCL) PRIMARY 6.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
vuln.today AI 4.8 MEDIUM

AC:H reflects the required non-default parser-reuse pattern and attacker-controlled document ordering; impacts are confined to partial confidentiality and integrity with no scope change.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (CIRCL).

CVSS VectorVendor: CIRCL

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.4%
Top 70% exploitable
Prevalence
Low
niche threat-intel conversion library used by MISP ecosystem integrators
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

More in Misp

View all
CVE-2018-19908 HIGH POC
8.8 Dec 06

An issue was discovered in MISP 2.4.9x before 2.4.99. Rated high severity (CVSS 8.8), this vulnerability is remotely exp

CVE-2022-29528 CRITICAL POC
9.8 Apr 20

An issue was discovered in MISP before 2.4.158. Rated critical severity (CVSS 9.8), this vulnerability is remotely explo

CVE-2022-48328 CRITICAL POC
9.8 Feb 20

app/Controller/Component/IndexFilterComponent.php in MISP before 2.4.167 mishandles ordered_url_params and additional_de

CVE-2026-44381 CRITICAL POC
9.3 May 13

SQL injection in MISP threat intelligence platform versions prior to 2.5.37 allows remote unauthenticated attackers to m

CVE-2022-29534 HIGH POC
7.5 Apr 20

An issue was discovered in MISP before 2.4.158. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitab

CVE-2023-37306 HIGH POC
7.5 Jun 30

MISP 2.4.172 mishandles different certificate file extensions in server sync. Rated high severity (CVSS 7.5), this vulne

CVE-2021-41326 CRITICAL
9.8 Sep 17

In MISP before 2.4.148, app/Lib/Export/OpendataExport.php mishandles parameter data that is used in a shell_exec call. R

CVE-2018-12649 CRITICAL
9.8 Jun 22

An issue was discovered in app/Controller/UsersController.php in MISP 2.4.92. Rated critical severity (CVSS 9.8), this v

CVE-2020-15411 CRITICAL
9.8 Jun 30

An issue was discovered in MISP 2.4.128. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable,

CVE-2020-29006 CRITICAL
9.8 Nov 24

MISP before 2.4.135 lacks an ACL check, related to app/Controller/GalaxyElementsController.php and app/Model/GalaxyEleme

CVE-2021-35502 CRITICAL
9.8 Jun 25

app/View/Elements/genericElements/IndexTable/Fields/generic_field.ctp in MISP 2.4.144 does not sanitize certain data rel

CVE-2021-39302 CRITICAL
9.8 Aug 19

MISP 2.4.148, in certain configurations, allows SQL injection via the app/Model/Log.php $conditions['org'] value. Rated

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy