MISP cullEmptyEvents CSRF Allows Irreversible Deletion of Events via GET Request
A cross-site request forgery (CSRF) vulnerability existed in the cullEmptyEvents action of MISP. The endpoint performed a state-changing and irreversible operation while accepting HTTP GET requests. Because bodyless GET requests are not subject to CakePHP's CSRF validation, an attacker could cause an authenticated MISP user with sufficient privileges to invoke the endpoint simply by causing their browser to load a crafted URL, for example through an embedded image or other automatically requested resource. Successful exploitation triggers the deletion of published empty events. The deletion is particularly significant because the operation uses skipBlocklist, meaning the removed events do not leave blocklist entries that could prevent or track their subsequent synchronization. This can result in unintended and potentially irreversible deletion of MISP event records without explicit user interaction. The vulnerability was addressed by restricting cullEmptyEvents to HTTP POST requests, ensuring that CakePHP's normal CSRF protections are applied to the operation.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-85236
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 16:25 UTC · Revision 1
Source evidence
MISP cullEmptyEvents CSRF Allows Irreversible Deletion of Events via GET Request
core-osv · Original sourcePublished 3 Sept 2026, 15:13 UTC
A cross-site request forgery (CSRF) vulnerability existed in the cullEmptyEvents action of MISP. The endpoint performed a state-changing and irreversible operation while accepting HTTP GET requests. Because bodyless GET requests are not subject to CakePHP's CSRF validation, an attacker could cause an authenticated MISP user with sufficient privileges to invoke the endpoint simply by causing their browser to load a crafted URL, for example through an embedded image or other automatically requested resource. Successful exploitation triggers the deletion of published empty events. The deletion is particularly significant because the operation uses skipBlocklist, meaning the removed events do not leave blocklist entries that could prevent or track their subsequent synchronization. This can result in unintended and potentially irreversible deletion of MISP event records without explicit user interaction. The vulnerability was addressed by restricting cullEmptyEvents to HTTP POST requests, ensuring that CakePHP's normal CSRF protections are applied to the operation.
osv:CVE-2026-85236
Complete source record
{
"id": "b9d489e9e8380013159ea0ead6684f0edd9cf3ffd1d6b4235c7eb6e29a1faed5",
"url": "https://osv.dev/vulnerability/CVE-2026-85236",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "MISP cullEmptyEvents CSRF Allows Irreversible Deletion of Events via GET Request",
"summary": "A cross-site request forgery (CSRF) vulnerability existed in the cullEmptyEvents action of MISP. The endpoint performed a state-changing and irreversible operation while accepting HTTP GET requests. Because bodyless GET requests are not subject to CakePHP's CSRF validation, an attacker could cause an authenticated MISP user with sufficient privileges to invoke the endpoint simply by causing their browser to load a crafted URL, for example through an embedded image or other automatically requested resource. Successful exploitation triggers the deletion of published empty events. The deletion is particularly significant because the operation uses skipBlocklist, meaning the removed events do not leave blocklist entries that could prevent or track their subsequent synchronization. This can result in unintended and potentially irreversible deletion of MISP event records without explicit user interaction. The vulnerability was addressed by restricting cullEmptyEvents to HTTP POST requests, ensuring that CakePHP's normal CSRF protections are applied to the operation.",
"evidence": "osv:CVE-2026-85236",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-85236",
"aliases": [
"CVE-2026-85236"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/misp/misp",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "2b6b3ac90"
},
{
"fixed": "50106c9a0"
},
{
"fixed": "66ecb5acb"
},
{
"fixed": "9c1346ce1"
},
{
"fixed": "cfc8b8a6d"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:misp-project:misp:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"last_affected": "2.5.45"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "2b6b3ac90"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "50106c9a0"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "66ecb5acb"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "9c1346ce1"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "cfc8b8a6d"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-85236.json"
}
}
],
"modified": "2026-10-28T02:30:37.487359298Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/85xxx/CVE-2026-85236.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-85236",
"https://github.com/MISP/MISP/commit/2b6b3ac90",
"https://github.com/MISP/MISP/commit/50106c9a0",
"https://github.com/MISP/MISP/commit/66ecb5acb",
"https://github.com/MISP/MISP/commit/9c1346ce1",
"https://github.com/MISP/MISP/commit/cfc8b8a6d",
"https://github.com/MISP/MISP"
],
"provider_metadata": {
"cwe_ids": [
"CWE-352"
],
"cna_assigner": "CIRCL",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/85xxx/CVE-2026-85236.json"
}
},
"related_cves": [
{
"value": "CVE-2026-85236",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 504645,
"published_at": "2026-09-03T15:13:00.493+00:00"
}