# CVE-2026-90955: MISP CLI Shell Audit Logs Lose User Identity and CLI Marker After First Lazy Model Load

> MISP CLI shell fails to correctly log user identity and CLI markers, potentially obscuring audit trails and allowing actions to appear as standard web activity.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-wxf7-wrjx-26cc

## What is CVE-2026-90955?

CVE-2026-90955 is a medium-severity vulnerability in MISP, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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

Weakness: CWE-778 (Insufficient Logging), CWE-223 (Omission of Security-relevant Information)

## Which versions are affected by CVE-2026-90955?


## How do I fix CVE-2026-90955?

No fix has been published for CVE-2026-90955 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-90955 being exploited?

There is no known exploitation of CVE-2026-90955 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90955 and fix it if it is affected.

What it is: CVE-2026-90955 is a medium-severity vulnerability in MISP, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90955 in the wild and no public exploit code.

Affected product: MISP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90955/ (Markdown: https://insights.sbomify.com/CVE-2026-90955/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90955
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90955
- OSV: https://osv.dev/vulnerability/CVE-2026-90955

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90955/
Summaries are generated and may contain mistakes; the official description above is the record.