# CVE-2026-95658: MISP CSRF vulnerability in workflow moduleStatelessExecution allows cross-site execution of workflow modules

> An attacker can trick an authenticated MISP administrator into executing arbitrary workflow modules, allowing modification of security blocklists and warninglists.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-5fvj-qq2x-32vr

## What is CVE-2026-95658?

CVE-2026-95658 is a medium-severity vulnerability in MISP, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

MISP's WorkflowsController exposed the moduleStatelessExecution action in the Security component's unlockedActions list. In CakePHP, listing an action in unlockedActions disables both the CSRF token check and the field hash validation for that action. Because moduleStatelessExecution executes a workflow module's exec() method with caller-supplied input and parameters, the absence of CSRF protection allowed an attacker to craft a cross-site form post (or equivalent cross-origin request) that, when submitted by an authenticated site administrator, would cause the administrator's browser to invoke the action on the MISP instance. 

The attacker could select any workflow module to execute, including action modules that write blocklist and warninglist entries, and supply arbitrary input and parameters of their choosing. This constitutes a cross-site request forgery (CSRF) vulnerability with high integrity impact on the MISP instance's security-related data. 

The vulnerability was identified during an internal security review and was not externally reported. The fix is included in MISP v2.5.47.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-95658?


## How do I fix CVE-2026-95658?

No fix has been published for CVE-2026-95658 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-95658 being exploited?

There is no known exploitation of CVE-2026-95658 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-95658 and fix it if it is affected.

What it is: CVE-2026-95658 is a medium-severity vulnerability in MISP, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-95658 in the wild and no public exploit code.

Affected product: MISP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-95658/ (Markdown: https://insights.sbomify.com/CVE-2026-95658/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-95658
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-95658
- OSV: https://osv.dev/vulnerability/CVE-2026-95658

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-95658/
Summaries are generated and may contain mistakes; the official description above is the record.