CVE-2026-10860: MISP CRUDComponent delete validation bypass via operator precedence error

Published Jun 4, 2026
·
Updated

A logic error in the MISP CRUD component delete handler allowed validation failures to be bypassed when requests used the HTTP DELETE method. Due to missing parentheses in the delete condition, the expression was evaluated as ($validationError === null && POST) || DELETE, meaning a DELETE request could proceed even when the delete validation callback had rejected the operation. An authenticated attacker with access to an affected delete endpoint could abuse this flaw to delete records that should have been protected by application-level validation or authorization checks.

Affected Software

2 affected components
Misp Misp
Misp-project Misp<2.5.39

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Modify the delete handler code so the delete validation callback is enforced for DELETE requests. Correct the operator precedence in the delete condition (e.g., add parentheses or restructure the conditional) so that the validation result is required before allowing a DELETE to proceed.

    MISP CRUD component (delete handler) delete validation operator precedence / conditional = ensure validation callback result is applied to DELETE requests (add parentheses or otherwise correct the conditional)
  2. Compensating control

    Until the code fix is deployed, restrict access to affected delete endpoints (for example with firewall rules, ACLs, or network segmentation) to only trusted IPs or internal management networks and require strong authentication/authorization for delete operations.

  3. Operational

    Audit recent delete requests and application logs for unauthorized or unexpected deletions, restore any improperly deleted records from backups if needed, and review authorization/validation callback configurations for other CRUD handlers.

Event History

Jun 4, 2026
CVE Published
via MITRE·01:34 PM
Data Sourced
via MITRE·01:34 PM
DescriptionWeakness
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
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-10860?

The severity of CVE-2026-10860 is rated high with a CVSS score of 7.9.

2

What type of vulnerability is CVE-2026-10860?

CVE-2026-10860 is a logic error vulnerability in the MISP CRUD component that allows validation bypass.

3

How do I fix CVE-2026-10860?

To fix CVE-2026-10860, update the MISP software to the latest version where the logic error in the delete handler is corrected.

4

What are the potential impacts of CVE-2026-10860?

The potential impacts of CVE-2026-10860 include unauthorized deletions of resources due to bypassing validation checks.

5

When was CVE-2026-10860 published?

CVE-2026-10860 was published on June 4, 2026.

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