# CVE-2026-10719: Open Seachest/Seachest NVMe show Format Descriptors Vulnerability

> A malicious NVMe device can trigger an out-of-bounds write in openSeaChest, potentially allowing code execution or denial of service.

- **Severity:** Low 1.8 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:L/S:N/AU:Y/R:A/V:D/RE:L/U:Clear`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-6rch-j2wj-8h2j

## What is CVE-2026-10719?

CVE-2026-10719 is a low-severity memory corruption vulnerability, published on 2 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out of bounds write in openSeaChest’s --showSupportedFormats in Seagate’s openSeaChest v25.05.3 on all supported platforms allows for writing 1 extra byte outside of allocated memory which sets a value to 1 via a maliciously crafted NVMe device with a bogus value in the namespace FLBAS byte.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-10719 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10719 is a low-severity memory corruption vulnerability, published on 2 Jun 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-10719 in the wild and no public exploit code.

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-10719/ (Markdown: https://insights.sbomify.com/CVE-2026-10719/index.md)
```

## Sources

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

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