CVE-2026-73162
Received Received - Intake

CSRF Vulnerability in MISP cti-transmute Account Operations

Publication date: 2026-08-11

Last updated on: 2026-08-11

Assigner: 5a6e4751-2f3f-4070-9419-94fb35b644e8

Description
Affected versions of MISP cti-transmute expose several state-changing account operations as GET requests: * /account/follow * /account/delete_notification * /account/mark_notification_read * /account/mark_all_read These endpoints require authentication, but before the fix they could be invoked with simple GET requests. That makes them susceptible to cross-site request forgery because a third-party site can induce the victim’s browser to send authenticated GET requests automatically. The patch converts the actions to POST or DELETE and updates the frontend to include an X-CSRFToken header, providing explicit CSRF protection for those state-changing operations.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-11
Last Modified
2026-08-11
Generated
2026-08-11
AI Q&A
2026-08-11
EPSS Evaluated
N/A
NVD
CVE-2026-73162
EUVD
EUVD-2026-55994

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
misp cti-transmute to 2026-73162 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves state-changing account operations in MISP cti-transmute that were exposed as GET requests. These include actions like following/unfollowing accounts and managing notifications. GET requests are vulnerable to cross-site request forgery (CSRF) because browsers automatically send authenticated GET requests when visiting malicious sites.

Detection Guidance

Check if the affected endpoints (/account/follow, /account/delete_notification, /account/mark_notification_read, /account/mark_all_read) are accessible via GET requests without proper CSRF protection. Use tools like curl to test these endpoints with GET requests while authenticated.

Impact Analysis

An attacker could trick you into visiting a malicious website, which would automatically trigger authenticated GET requests to perform actions like unfollowing your account or deleting notifications without your knowledge. This could lead to unauthorized changes in your account state.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by exposing users to CSRF attacks that may lead to unauthorized state changes in their accounts. Unauthorized actions like deleting notifications or following/unfollowing accounts could compromise data integrity and user privacy, which are key concerns under these regulations.

Mitigation Strategies

Update MISP cti-transmute to the patched version where these endpoints use POST or DELETE methods and include X-CSRFToken headers. Ensure all state-changing operations are restricted to these methods and verify CSRF token implementation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-73162. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart