Quick answers
- Is CVE-2026-103237 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103237 being exploited in the wild.
- How severe is CVE-2026-103237?
- Informational severity, published 30 September 2026.
- Which products and versions are affected?
- Misp before 2.5.48.
- Is there a fix for CVE-2026-103237?
- A patch was published on 2026-09-25: Fix committed to MISP repository (commit 9485ae40d) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-103237 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-103237?
- Check whether you run Misp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an improper input validation flaw in MISP's ORM save path. When handling requests to attribute add/edit, event edit, sighting capture, shadow attribute proposal, and other endpoints, the application sanitizes the top-level record (stripping IDs, pinning event_id) but the underlying ORM's set() method prioritizes a nested key matching the model alias, ignoring the sanitized outer fields. An authenticated user can embed a malicious nested block under the model alias to bypass sanitization and modify arbitrary database rows.
Affected products
- MISP MISP before 2.5.48
Timeline
- 2026-09-30: disclosed: Vulnerability published on NVD
- 2026-09-25: patched: Fix committed to MISP repository (commit 9485ae40d)