# CVE-2026-95667: MISP Installer Log and FIFO Created World-Readable, Exposing Sensitive Credentials

> Local attackers can read world-readable installer logs to steal sensitive credentials, potentially leading to privilege escalation.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-qjpg-gmh7-3ch6

## What is CVE-2026-95667?

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

### Official description

The MISP installer scripts (for Debian 12, Debian 13, Ubuntu 24.04, and RHEL 9.4) create a log file at /var/log/misp_install.log and a named pipe (FIFO) at /var/log/misp_install.log.pipe to capture all installer output. The log captures highly sensitive data including the generated admin password, database passwords, GPG passphrase, and supervisor password. However, the log file was created by the tee command under the system default umask, resulting in world-readable permissions (typically 0644). Similarly, the FIFO was created with mkfifo without an explicit mode, also inheriting the default umask and remaining world-readable during the window before it was unlinked. 

Any local unprivileged user on the system could read the log file or the FIFO to obtain these credentials. 

Additionally, the log file was not removed before creation, meaning a pre-existing symlink in /var/log could have been used to redirect the write to an arbitrary location.

Version affected: <2.5.47

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-95667 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95667 is a medium-severity vulnerability in MISP, published on 22 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-95667 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-95667/ (Markdown: https://insights.sbomify.com/CVE-2026-95667/index.md)
```

## Sources

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

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