---
id: CVE-2026-95667
title: >-
  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
summary: >-
  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 …
severity: medium
cvss: 6.9
cvssVector: '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'
cwe:
  - CWE-22
  - CWE-732
vendor: MISP
product: MISP
affected:
  - MISP < 2.5.47
published: '2026-09-22'
updated: '2026-09-22'
sourceUpdated: '2026-09-22T16:18:21.917'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-95667'
references:
  - url: 'https://github.com/MISP/MISP/commit/d5d72ab38'
    label: 5a6e4751-2f3f-4070-9419-94fb35b644e8
tags:
  - nvd
  - cve.org
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-09-22T15:32:35.402501Z'
cvssSource: cna
ingestedAt: '2026-09-22T14:04:19.593Z'
epss: 0.0018
epssPercentile: 0.07831
---

## Overview

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

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.