Quick answers
- Is CVE-2026-10717 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10717 being exploited in the wild.
- How severe is CVE-2026-10717?
- 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-10717?
- 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-10717 attacked?
- It is attacked with local access or with physical access, in a software library.
- Am I affected by CVE-2026-10717?
- 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 and read vulnerability exists in Seagate openSeaChest v25.05.3 within the --showSCSIDefects command. The issue stems from improper validation of the defect response length provided by a SCSI device. An attacker can exploit this by connecting a maliciously crafted SCSI device or a drive with an exceptionally large defect list to a system running the utility. Successful exploitation requires high privileges to execute the diagnostic tool and physical or local access to the hardware interface, potentially leading to memory corruption or local code execution.
Affected products
- Seagate openSeaChest 25.05.3
Timeline
- 2026-06-02: disclosed: CVE published by Seagate Technology