Cross-Document Parser State Contamination in misp-stix
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 p
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-77761
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 19:28 UTC · Revision 1
Source evidence
Cross-Document Parser State Contamination in misp-stix
core-osv · Original sourcePublished 21 Aug 2026, 10:11 UTC
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 p
osv:CVE-2026-77761
Complete source record
{
"id": "295ecb0b736a613f7e9d997ece90337295732bc07cded0f37c553a59d8d7d545",
"url": "https://osv.dev/vulnerability/CVE-2026-77761",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Cross-Document Parser State Contamination in misp-stix",
"summary": "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 p",
"evidence": "osv:CVE-2026-77761",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-77761",
"aliases": [
"CVE-2026-77761"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/misp/misp-stix",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "f08373dd"
},
{
"fixed": "ad4f0a65"
},
{
"fixed": "f6593931"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"last_affected": "2026.7.8"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"fixed": "f08373dd"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "ad4f0a65"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "f6593931"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-77761.json"
}
}
],
"modified": "2026-10-28T02:30:31.677166893Z",
"provider": "osv",
"references": [
"https://github.com/MISP/misp-stix/",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/77xxx/CVE-2026-77761.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-77761",
"https://github.com/MISP/misp-stix/commit/ad4f0a65.patch",
"https://github.com/MISP/misp-stix/commit/f08373dd",
"https://github.com/MISP/misp-stix/commit/f6593931"
],
"provider_metadata": {
"cwe_ids": [
"CWE-459"
],
"cna_assigner": "CIRCL",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/77xxx/CVE-2026-77761.json"
}
},
"related_cves": [
{
"value": "CVE-2026-77761",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 498723,
"published_at": "2026-08-21T10:11:54.84+00:00"
}