Quick answers
- Is CVE-2026-10719 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10719 being exploited in the wild.
- How severe is CVE-2026-10719?
- Informational severity, with a CVSS score of 1.8, published 2 June 2026.
- Which products and versions are affected?
- Seagate openSeaChest 25.05.3.
- Is there a fix for CVE-2026-10719?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-10719 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-10719?
- Check whether you run Seagate openSeaChest 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.
Technical details
An out-of-bounds (OOB) write vulnerability exists in the --showSupportedFormats function of Seagate openSeaChest v25.05.3. The flaw is triggered by a maliciously crafted NVMe device that provides a bogus value in the namespace Format LBA Size (FLBAS) byte. This causes the application to write one extra byte (setting a value to 1) outside of the allocated memory buffer. Exploitation requires local access and high privileges to interface with the hardware device, and the impact is limited to minor integrity and availability issues.
Affected products
- Seagate openSeaChest 25.05.3
Timeline
- 2026-06-02: disclosed: Initial publication of the CVE record