Medium · CVSS 4.6CVE-2026-90955

MISP CLI Shell Audit Logs Lose User Identity and CLI Marker After First Lazy Model LoadCVE-2026-90955

Answer in brief

CVE-2026-90955 records a Medium severity (CVSS 4.6) vulnerability in MISP CLI Shell Audit Logs Lose User Identity and CLI Marker After First Lazy Model Load. The current sources do not mark it as known exploited. The current feed maps MISP/MISP (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 14, 2026Updated Sep 16, 2026Source checked Oct 29, 2026First seen by HOL Sep 14, 2026Material review Sep 16, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 4.6
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 4.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps MISP/MISP (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
MISP/MISPgeneric	>=0 <2.5.46	2.5.46

Recommended response

Check inventory. Check lockfiles and deployed manifests for MISP/MISP.
Review the reported fix. Source-reported solution: The fix introduces a process-wide static identity (setShellUser) on SysLogLogableBehavior that is resolved at write time rather than at setup time, so it survives lazy model loads that re-run setup() on the singleton. The behavior appends 'via CLI' to the log description for shell-originated rows, mirroring the request_type = CLI marker in the new audit engine. The CLI shell now publishes the impersonated user through both Configure::write('CurrentUserId') and SysLogLogableBehavior::setShellUser() before any write. Explicit extralog calls were added for CLI user edit, disable, and delete operations so the default audit engine records them the same way the web path does. Background jobs that publish no user continue to log as SYSTEM without a CLI marker.

Evidence timeline and material changes

Published upstream
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 14, 2026

Sources and claim methodology

GitHub security advisorygithub.com

Upstream source description

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

Quoted source text, attributed separately from HOL analysis.

Package

Affected range

Fixed version

MISP/MISPgeneric

>=0 <2.5.46

2.5.46

Recommended response

Check inventory. Check lockfiles and deployed manifests for MISP/MISP.

Review the reported fix. Source-reported solution: The fix introduces a process-wide static identity (setShellUser) on SysLogLogableBehavior that is resolved at write time rather than at setup time, so it survives lazy model loads that re-run setup() on the singleton. The behavior appends 'via CLI' to the log description for shell-originated rows, mirroring the request_type = CLI marker in the new audit engine. The CLI shell now publishes the impersonated user through both Configure::write('CurrentUserId') and SysLogLogableBehavior::setShellUser() before any write. Explicit extralog calls were added for CLI user edit, disable, and delete operations so the default audit engine records them the same way the web path does. Background jobs that publish no user continue to log as SYSTEM without a CLI marker.

Sources and claim methodology

Upstream source description

Quoted source text, attributed separately from HOL analysis.