CVE-2026-95658: MISP WorkflowsController CSRF vulnerability in moduleStatelessExecution

CVE-2026-95658 · Severity: info · Published 2026-09-22

MISP is a threat intelligence platform used by security teams to manage and share indicator data. An improper configuration in the WorkflowsController allowed attackers to bypass CSRF protection on a critical action that executes workflow modules. An authenticated administrator tricked into visiting a malicious website could have their browser execute arbitrary workflow modules on the MISP instance, including modules that modify security blocklists and warning lists without authorization.

Technologies: Misp. Vendors: Misp.

Quick answers

Is CVE-2026-95658 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-95658 being exploited in the wild.
How severe is CVE-2026-95658?
Informational severity, published 22 September 2026.
Which products and versions are affected?
Misp before 2.5.47.
Is there a fix for CVE-2026-95658?
A patch was published on 2026-09-22: Fix included in MISP v2.5.47 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-95658 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-95658?
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 moduleStatelessExecution action was listed in CakePHP's Security component unlockedActions, which disables CSRF token validation. Because the action accepts caller-supplied input and parameters to execute arbitrary workflow modules—including action modules that write to blocklists and warninglists—an attacker could craft a cross-site form post that, when submitted by an authenticated administrator, would execute malicious modules with attacker-controlled input. The vulnerability was fixed in MISP v2.5.47 by removing the action from unlockedActions and implementing proper CSRF token handling via X-CSRF-Token headers.

Affected products

  • MISP MISP before 2.5.47

Timeline

  • 2026-09-22: disclosed
  • 2026-09-22: patched: Fix included in MISP v2.5.47

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.