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

Published Jun 12, 2026
·
Updated

MISP contains an insecure default configuration in which the Security.checksecfetchsiteheader 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.checksecfetchsiteheader mitigates this issue, although operators of multi-homed MISP deployments should validate the setting before enforcing it.

Affected Software

1 affected component
Misp Project Misp

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Enable Security.check_sec_fetch_site_header in MISP's security configuration to require and enforce the browser-provided Sec-Fetch-Site header for state-changing requests (e.g., POST, PUT, AJAX).

    MISP Security.check_sec_fetch_site_header = enabled
  2. Operational

    For multi-homed MISP deployments, validate and test the impact of enabling Security.check_sec_fetch_site_header in a staging or test environment before enforcing it in production to ensure it does not disrupt legitimate cross-origin workflows.

Event History

Jun 12, 2026
CVE Published
via MITRE·07:44 PM
Data Sourced
via MITRE·07:44 PM
DescriptionWeakness
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-54359?

The severity of CVE-2026-54359 is rated high with a CVSS score of 7.1.

2

How does CVE-2026-54359 affect MISP users?

CVE-2026-54359 affects MISP users by exposing them to Cross-Site Request Forgery (CSRF) attacks when the Sec-Fetch-Site protection is disabled.

3

How can I mitigate CVE-2026-54359?

To mitigate CVE-2026-54359, enable the Security.check_sec_fetch_site_header control to protect against CSRF attacks.

4

When was CVE-2026-54359 published?

CVE-2026-54359 was published on June 12, 2026.

5

What type of vulnerability is CVE-2026-54359?

CVE-2026-54359 is classified as a Cross-Site Request Forgery (CSRF) vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203