# CVE-2026-111555: Luksmeta: missing slot-range validation permits out-of-gap device i/o

> An attacker with privileged access can corrupt encrypted storage by bypassing slot-range validation in luksmeta, causing persistent data loss.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-109739, DEBIAN-CVE-2026-111555, GHSA-jjpj-mrvg-445j, UBUNTU-CVE-2026-111555

## What is CVE-2026-111555?

CVE-2026-111555 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in luksmeta. Improper boundary validation of metadata slots allows an attacker capable of supplying or modifying a disk header to redirect wipe or load operations outside the intended metadata area. An attacker could exploit this vulnerability by providing a crafted header with valid checksums to overwrite or zero out encrypted payload data, resulting in persistent data loss and corrupted storage. Exploitation typically requires privileged access to modify raw block devices or the ability to induce an administrator to process an untrusted disk image.

Weakness: CWE-1285 (Improper Validation of Specified Index, Position, or Offset in Input)

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


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

Apply the vendor's patch.

## Is CVE-2026-111555 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111555 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-111555 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-111555/ (Markdown: https://insights.sbomify.com/CVE-2026-111555/index.md)
```

## Sources

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

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