CVE-2026-90955: MISP CLI Shell Audit Logs Lose User Identity and CLI Marker After First Lazy Model Load
Affected versions of MISP’s interactive CLI shell do not reliably preserve the identity of the impersonated MISP user across audit logging.
The shell is designed to run actions as a supplied MISP user ID. However, the legacy SysLogLogable behavior stored that identity in behavior-instance state that could be overwritten when another model lazily attached the shared behavior. Consequently, subsequent CLI writes could lose the intended user attribution and be logged incorrectly. The commit also notes that CLI-originated records lacked a CLI marker, making them appear similar to ordinary web actions by that user.
Version affected: ≤2.5.45
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
MISP interactive CLI shellto a version that resolves this vulnerability.Fixed in ≤2.5.45
Event History
Frequently Asked Questions
Which deployments are affected?
The issue affects MISP versions 2.5.45 and earlier when using the interactive CLI shell. It concerns audit logging for actions run while impersonating a supplied MISP user ID.
When does incorrect audit attribution occur?
It can occur after another model lazily attaches the shared legacy SysLogLogable behavior, overwriting behavior-instance state that held the impersonated user identity. Subsequent CLI writes may then be logged with incorrect or missing user attribution.
Why can this make investigations harder?
CLI-originated audit records lacked a CLI marker, so they could appear similar to ordinary web actions attributed to that user. This can obscure whether an action originated from the interactive CLI shell.