Is CVE-2026-112188 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-112188 being exploited in the wild.

How severe is CVE-2026-112188?

Informational severity, published 19 October 2026.

Which products and versions are affected?

MISP Project MISP before 2.5.48.

Is there a fix for CVE-2026-112188?

Yes: fixed in 2.5.48. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-112188 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-112188?

Check whether you run MISP Project MISP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-112188: MISP server settings information disclosure

CVE-2026-112188 · Severity: info · Published 2026-10-19

MISP is a threat intelligence sharing platform that stores sensitive server configuration such as encryption keys and database passwords. An authenticated attacker can bypass redaction protections by requesting configuration branch names instead of specific settings, causing the server to expose secrets including security salts, Redis passwords, and API keys.

Technologies: MISP Project MISP. Vendors: MISP Project.

Quick answers

Is CVE-2026-112188 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-112188 being exploited in the wild.
How severe is CVE-2026-112188?: Informational severity, published 19 October 2026.
Which products and versions are affected?: MISP Project MISP before 2.5.48.
Is there a fix for CVE-2026-112188?: Yes: fixed in 2.5.48. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-112188 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-112188?: Check whether you run MISP Project MISP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 2.5.48

Technical details

The vulnerability exists in the server settings lookup mechanism (Server::getSettingData()) which fails to validate that resolved configuration names refer to leaf settings rather than branch nodes. Branch nodes lack redaction flags, allowing attackers to bypass the redaction check in the /servers/getSetting and /servers/serverSettingsEdit endpoints. An authenticated user can supply a branch name (e.g., "Security", "MISP", "Plugin") to retrieve entire configuration subtrees containing sensitive values.

Affected products

MISP Project MISP before 2.5.48

Timeline

2026-10-19: disclosed
2026-10-19: patched

References

https://github.com/MISP/MISP/commit/30b849102

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.