Live › vulnerability › CVE-2026-112188
Go to dashboardMISP's server settings lookup returns an entire configuration branch when given a branch name, skipping the redaction check. An authenticated user can therefore read secrets such as the security salt, Redis passwords and plugin API keys.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Any MISP instance running a version below is exposed to users who hold a valid account and can reach the server settings endpoints. Instances where only trusted administrators have accounts carry lower practical risk but should still be upgraded.
2.5.48No product ranges from the sources yet.
2.5.482.5.48 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
MISP contains a vulnerability in its server settings lookup mechanism that allows an authenticated user to retrieve sensitive configuration data that should have been redacted.
The settings lookup function resolves a dotted setting name to a node in the configuration tree. When a branch name (such as Security, MISP, or Plugin) is supplied instead of a specific leaf setting, the function returns the entire sub-tree. Because a branch node does not carry a redaction flag, the redaction check in the settings retrieval endpoint is bypassed, and the full branch contents are returned to the caller. This exposes sensitive values including the security salt, Redis connection passwords, and plugin API keys.
A second endpoint that edits server settings similarly reads the entire configuration store when a branch name is resolved, returning all settings to the caller.
The impact is disclosure of sensitive server configuration secrets to any user who can access the server settings endpoints.
Affected versions: <2.5.48.
This page as .md · .json · in your agent: get_signal("CVE-2026-112188")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.