# CVE-2026-54359: MISP automation endpoints may be exposed to CSRF when Sec-Fetch-Site protection is disabled by default

> Attackers can perform unauthorized actions on MISP via CSRF due to disabled Sec-Fetch-Site checks, requiring configuration changes to mitigate.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:L/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:** 12 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-g8rg-9w6v-v9gv

## What is CVE-2026-54359?

CVE-2026-54359 is a high-severity vulnerability in misp, published on 12 Jun 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 contains an insecure default configuration in which the Security.check_sec_fetch_site_header control is disabled. When this setting is disabled, state-changing requests such as POST, PUT, or AJAX requests are not restricted based on the browser-provided Sec-Fetch-Site header. A remote unauthenticated attacker could craft a malicious web page that causes an authenticated MISP user’s browser to issue cross-site requests to MISP automation endpoints. If successful, the forged requests may be processed with the privileges of the victim user, potentially allowing unauthorized modification of MISP data or configuration. Enabling Security.check_sec_fetch_site_header mitigates this issue, although operators of multi-homed MISP deployments should validate the setting before enforcing it.

Weakness: CWE-352 (Cross-Site Request Forgery), CWE-1188 (Initialization of a Resource with an Insecure Default)

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


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

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

## Is CVE-2026-54359 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54359 is a high-severity vulnerability in misp, published on 12 Jun 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-54359 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-54359/ (Markdown: https://insights.sbomify.com/CVE-2026-54359/index.md)
```

## Sources

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

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