# CVE-2026-112188: MISP Server Settings Lookup Exposes Sensitive Configuration Data via Branch Name Resolution

> Authenticated users can retrieve sensitive server configuration secrets, including passwords and API keys, by exploiting a flaw in the settings lookup mechanism.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-mp6x-6c2r-xcxv

## What is CVE-2026-112188?

CVE-2026-112188 is a high-severity vulnerability in MISP, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-285 (Improper Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-112188 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112188 is a high-severity vulnerability in MISP, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-112188 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-112188/ (Markdown: https://insights.sbomify.com/CVE-2026-112188/index.md)
```

## Sources

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

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