MISP Correlation Authorization Bypass Exposes Restricted Event and Attribute Data
MISP contains an authorization flaw in its correlation handling during attribute searches. When a user performs an attribute search that triggers correlation lookups, the system authorized access to correlated attributes and events based on a stale distribution snapshot stored on the correlation row rather than the live event access control list. Because the correlation row's distribution columns are a point-in-time copy that lacks a published flag, the authorization check becomes incorrect when an event is subsequently restricted (for example, its sharing group is changed or it is unpublished). As a result, an authenticated user could retrieve attributes and event details belonging to events they no longer have permission to view. Preconditions: - An authenticated user with at least read access to some events in the instance. - The existence of correlations between events, at least one of which has been restricted after the correlation was created. Impact: - Confidentiality: exposure of attribute values and event metadata that the user is not authorized to access. Affected versions: MISP prior to v2.5.48.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-104912
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 10:54 UTC · Revision 1
Source evidence
MISP Correlation Authorization Bypass Exposes Restricted Event and Attribute Data
core-osv · Original sourcePublished 2 Oct 2026, 16:04 UTC
MISP contains an authorization flaw in its correlation handling during attribute searches. When a user performs an attribute search that triggers correlation lookups, the system authorized access to correlated attributes and events based on a stale distribution snapshot stored on the correlation row rather than the live event access control list. Because the correlation row's distribution columns are a point-in-time copy that lacks a published flag, the authorization check becomes incorrect when an event is subsequently restricted (for example, its sharing group is changed or it is unpublished). As a result, an authenticated user could retrieve attributes and event details belonging to events they no longer have permission to view. Preconditions: - An authenticated user with at least read access to some events in the instance. - The existence of correlations between events, at least one of which has been restricted after the correlation was created. Impact: - Confidentiality: exposure of attribute values and event metadata that the user is not authorized to access. Affected versions: MISP prior to v2.5.48.
osv:CVE-2026-104912
Complete source record
{
"id": "3ab67029baafaf1dfbc17d62f88c0c8f1906ffb443755d62bf0ce72d2b8b06ed",
"url": "https://osv.dev/vulnerability/CVE-2026-104912",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "MISP Correlation Authorization Bypass Exposes Restricted Event and Attribute Data",
"summary": "MISP contains an authorization flaw in its correlation handling during attribute searches. When a user performs an attribute search that triggers correlation lookups, the system authorized access to correlated attributes and events based on a stale distribution snapshot stored on the correlation row rather than the live event access control list. Because the correlation row's distribution columns are a point-in-time copy that lacks a published flag, the authorization check becomes incorrect when an event is subsequently restricted (for example, its sharing group is changed or it is unpublished). As a result, an authenticated user could retrieve attributes and event details belonging to events they no longer have permission to view. Preconditions: - An authenticated user with at least read access to some events in the instance. - The existence of correlations between events, at least one of which has been restricted after the correlation was created. Impact: - Confidentiality: exposure of attribute values and event metadata that the user is not authorized to access. Affected versions: MISP prior to v2.5.48.",
"evidence": "osv:CVE-2026-104912",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-104912",
"aliases": [
"CVE-2026-104912"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/misp/misp",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "63d46c54ccccd646fa352ee74d218f618ccce75b"
},
{
"fixed": "100235bd9"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "2.5.48"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"fixed": "100235bd9"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v2.5.47",
"v2.5.46",
"v2.5.45",
"v2.5.44",
"v2.5.43",
"v2.5.42",
"v2.5.41",
"v2.5.40",
"v2.5.39",
"v2.5.37",
"v2.5.36",
"v2.5.35",
"v2.5.34",
"v2.5.33",
"v2.5.32",
"v2.5.31",
"v2.5.30",
"v2.5.29",
"v2.5.28",
"v2.5.27",
"v2.5.26",
"v2.5.25",
"v2.5.24",
"v2.5.23",
"v2.5.22",
"v2.5.21",
"v2.5.20",
"v2.5.19",
"v2.5.18",
"v2.5.17",
"v2.5.16",
"v2.5.15",
"v2.5.12",
"v2.5.14",
"v2.5.13",
"v2.5.11",
"v2.5.10",
"v2.5.9",
"v2.5.8",
"v2.5.7",
"v2.5.0",
"v2.4.196",
"v2.4.195",
"v2.4.194",
"v2.4.193",
"v2.4.192",
"v2.4.191",
"v2.4.190",
"v2.4.189",
"v2.4.188",
"v2.4.187",
"v2.4.186",
"v2.4.175",
"v2.4.185",
"v2.4.183",
"v2.4.184",
"v2.4.153",
"v2.4.152",
"v2.4.137",
"v2.4.136",
"v2.4.134",
"v2.4.133",
"v2.4.130",
"v2.4.128",
"v2.4.127",
"v2.4.125",
"v2.4.123",
"v2.4.122",
"v2.4.121",
"v2.4.120",
"v2.4.118",
"v2.4.111",
"rm",
"v2.4.110",
"v2.4.109",
"codename/tellurium",
"v2.4.107",
"v2.4.106",
"v2.4.102",
"v2.4.101",
"v2.4.100",
"v2.4.98",
"v2.4.96",
"v2.4.95",
"v2.4.94",
"v2.4.93",
"v2.4.91",
"v2.4.89",
"v2.4.88",
"v2.4.87",
"v2.4.86",
"v2.4.85",
"v2.4.83",
"v2.4.82",
"v2.4.80",
"v2.4.78",
"v2.4.65",
"v2.4.64",
"v2.4.63",
"v2.4.62",
"v2.4.61",
"v2.4.60",
"v2.4.59",
"v2.4.58",
"v2.4.57",
"v2.4.56",
"v2.4.54",
"v2.4.53",
"v2.4.52",
"v2.4.51",
"v2.4.50",
"v2.4.48",
"v2.4.47",
"v2.4.46",
"v2.4.45",
"v2.4.43",
"v2.4.39",
"v2.4.38",
"v2.4.37",
"v2.4.36",
"v2.4.35",
"v2.4.34",
"v2.4.27",
"v2.4.26",
"v2.4.25",
"v2.4.24",
"v2.4.23",
"v2.4.22",
"v2.4.21",
"v2.4.20",
"v2.4.18",
"v2.4.17",
"v2.4.16",
"v2.4.15",
"v2.4.14",
"v2.4.13",
"v2.4.11",
"v2.4.10",
"v2.4.9",
"v2.4.7",
"v2.4.5",
"v2.4.4",
"v2.4.3",
"v2.4.2",
"v2.4.1",
"v2.4.0",
"v2.3.0",
"v0.2"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-104912.json"
}
}
],
"modified": "2026-10-28T02:30:27.982016854Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/104xxx/CVE-2026-104912.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-104912",
"https://github.com/MISP/MISP/commit/100235bd9",
"https://github.com/MISP/MISP"
],
"provider_metadata": {
"cwe_ids": [
"CWE-284",
"CWE-862"
],
"cna_assigner": "CIRCL",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/104xxx/CVE-2026-104912.json"
}
},
"related_cves": [
{
"value": "CVE-2026-104912",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 494753,
"published_at": "2026-10-02T16:04:50.58+00:00"
}