Description
A vulnerability in MISP's event template handling allowed an authenticated user with permission to create or modify event templates to bypass validation of the template definition field.

The EventTemplate::beforeValidate() method only performed semantic validation when the supplied definition was already represented as an array. If a caller instead supplied a pre-encoded string, including malformed JSON or JSON representing an unexpected data type, the value bypassed validateDefinition() and only needed to satisfy the generic notBlank validation rule. As a result, an invalid event template definition could be stored persistently in the database.

When event templates were subsequently retrieved, EventTemplate::afterFind() attempted to decode the stored definition using JsonTool::decode() without handling decoding failures. A definition containing invalid JSON could therefore trigger an exception during retrieval. Because the event template index is available to all authenticated users, a single malicious or malformed template could make the event template listing and other functionality relying on EventTemplate queries return HTTP 500 errors until the offending database row was manually repaired.

Valid JSON representing an unexpected type, rather than the expected JSON object, could similarly result in invalid data reaching downstream consumers.

The vulnerability can therefore be exploited by a user capable of saving event templates to persist malformed template data and cause a persistent denial of service against event-template functionality for other users.

The patch enforces that event template definitions must be supplied as structured objects before saving and always applies semantic validation. On retrieval, malformed JSON and definitions that do not decode to the expected structure are caught, logged, and replaced with an empty definition, preventing a malformed database entry from breaking all event template queries.

 Poisoning doesn't seem reachable according to the lead developer.
Published: 2026-09-03
Score: 7.1 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

MISP's event template handling allows an authenticated user to supply a pre‑encoded string for the definition field. The system only performs semantic validation when the definition is already an array; a string bypasses this check and only satisfies a generic not‑blank rule. Consequently, malformed JSON or data of an unexpected type can be stored in the database, leading to server‑side errors when templates are retrieved. The weakness is a classical input validation flaw (CWE‑20). The impact is that a single malicious or misconstructed template can cause all event‑template queries to fail with HTTP 500 errors until the offending database row is repaired, providing a persistent denial of service for users relying on templating.

Affected Systems

The affected product is MISP, specifically the event‑template component in the MISP platform. No specific version range is listed, so any deployment suitable for creating or modifying event templates is impacted.

Risk and Exploitability

The CVSS score of 7.1 indicates a medium to high severity. EPSS is not available, and the flaw is not currently listed in the CISA KEV catalog. Exploitation requires an authenticated user with the right to create or modify event templates, a privilege commonly granted to analysts or administrators. Once leveraged, the attacker can persist malformed template data, causing repeated server errors for all users accessing the template index. The lack of defensive checks during retrieval means the exception is thrown before normal response handling, directly resulting in denial of service until the database entry is manually fixed.

Generated by OpenCVE AI on September 3, 2026 at 16:35 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the official MISP patch that enforces structured objects and applies semantic validation before saving event templates.
  • Identify and delete or correct any event template records in the database that store invalid or malformed definition data.
  • During remediation, restrict or revoke permissions to create or modify event templates to trusted users so that no new malformed entries can be introduced until the patch is fully deployed.

Generated by OpenCVE AI on September 3, 2026 at 16:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 03 Sep 2026 16:45:00 +0000

Type Values Removed Values Added
First Time appeared Misp
Misp misp
Vendors & Products Misp
Misp misp

Thu, 03 Sep 2026 15:45:00 +0000

Type Values Removed Values Added
Description A vulnerability in MISP's event template handling allowed an authenticated user with permission to create or modify event templates to bypass validation of the template definition field. The EventTemplate::beforeValidate() method only performed semantic validation when the supplied definition was already represented as an array. If a caller instead supplied a pre-encoded string, including malformed JSON or JSON representing an unexpected data type, the value bypassed validateDefinition() and only needed to satisfy the generic notBlank validation rule. As a result, an invalid event template definition could be stored persistently in the database. When event templates were subsequently retrieved, EventTemplate::afterFind() attempted to decode the stored definition using JsonTool::decode() without handling decoding failures. A definition containing invalid JSON could therefore trigger an exception during retrieval. Because the event template index is available to all authenticated users, a single malicious or malformed template could make the event template listing and other functionality relying on EventTemplate queries return HTTP 500 errors until the offending database row was manually repaired. Valid JSON representing an unexpected type, rather than the expected JSON object, could similarly result in invalid data reaching downstream consumers. The vulnerability can therefore be exploited by a user capable of saving event templates to persist malformed template data and cause a persistent denial of service against event-template functionality for other users. The patch enforces that event template definitions must be supplied as structured objects before saving and always applies semantic validation. On retrieval, malformed JSON and definitions that do not decode to the expected structure are caught, logged, and replaced with an empty definition, preventing a malformed database entry from breaking all event template queries.  Poisoning doesn't seem reachable according to the lead developer.
Title MISP Event Template Definition Validation Bypass Allows Persistent Denial of Service
Weaknesses CWE-20
References
Metrics cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: CIRCL

Published:

Updated: 2026-09-03T15:53:26.210Z

Reserved: 2026-09-03T15:37:38.995Z

Link: CVE-2026-85239

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Undergoing Analysis

Published: 2026-09-03T16:18:27.457

Modified: 2026-09-03T16:45:08.223

Link: CVE-2026-85239

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-03T16:26:23Z

Weaknesses
  • CWE-20

    Improper Input Validation