CVE-2026-91859
Received Received - Intake

Incorrect Access Log Data in MISP Due to Double Exception Handling

Vulnerability report for CVE-2026-91859, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-15

Last updated on: 2026-09-15

Assigner: CIRCL

Description

Affected versions of MISP can record incorrect access-log data for requests that terminate in an exception. Because CakeErrorController extends AppController, exception rendering runs the application startup path a second time. As a result, __accessMonitor() calls AccessLog::logRequest() twice for one HTTP request. The second deferred writer measures the error-controller execution instead of the original request and can overwrite the row created by the first pass. The corrupted fields include request duration, SQL query count, memory usage, and potentially the recorded query log. The bug was masked because the same model instance retained the ID of the first saved row, causing the later save to issue an UPDATE rather than insert an obvious duplicate row. Version affected: ≀2.5.45

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-15
Last Modified
2026-09-15
Generated
2026-09-15
AI Q&A
2026-09-15
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
misp misp to 2.5.45 (inc)
misp misp to 2.5.45 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-223 The product does not record or display information that would be important for identifying the source or nature of an attack, or determining if an action is safe.
CWE-778 When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in MISP (versions ≀2.5.45) causes incorrect access-log data to be recorded when a request ends in an exception. The error controller runs the application startup path a second time, leading to duplicate calls to logRequest(). The second call overwrites the original log with incorrect metrics like request duration, SQL query count, and memory usage from the error controller instead of the original request.

Impact Analysis

This vulnerability can misrepresent performance metrics and query logs in your MISP instance. It may lead to incorrect monitoring data, making it difficult to assess actual system performance or troubleshoot issues. The corrupted logs could also affect security audits or compliance reporting.

Mitigation Strategies

Update MISP to version 2.5.46 or later to address the logging issue caused by double execution of AppController::beforeFilter() during exception handling.

Chat Assistant

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

EPSS Chart