# CVE-2026-114038: Device-mapper-multipath: device-mapper-multipath: information disclosure via malformed format string


- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-114038, GHSA-7rmr-p966-7g82, UBUNTU-CVE-2026-114038

## What is CVE-2026-114038?

CVE-2026-114038 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 21 Oct 2026. 

### Official description

A flaw was found in device-mapper-multipath. A local user can trigger an out-of-bounds read by sending a command with a format string ending in a trailing percent character to the multipath daemon. This issue can allow the user to expose unintended daemon memory, leading to information disclosure, or cause the daemon to crash, resulting in a Denial of Service (DoS).

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Upgrade to a fixed version.

## Is CVE-2026-114038 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114038 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114038 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-114038/ (Markdown: https://insights.sbomify.com/CVE-2026-114038/index.md)
```

## Sources

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

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