Memory corruption via unchecked SCSI defect count
Published Jun 2, 2026 · Updated Jun 2, 2026
Out-of-bounds access in Seagate openSeaChest 25.05.3 and earlier and 26.03.0 through 26.03.1 allows local users to corrupt memory. The --showSCSIDefects path accepts an extreme device-reported defect count without a sufficient upper-bound check, then reads and writes beyond the allocated defect-list buffer. Exploitation requires elevated execution against a defective or malicious SCSI device; 26.03.1 remains affected only on 32-bit builds.
Summary
What happened
Out-of-bounds access in Seagate openSeaChest 25.05.3 and earlier and 26.03.0 through 26.03.1 allows local users to corrupt memory. The --showSCSIDefects path accepts an extreme device-reported defect count without a sufficient upper-bound check, then reads and writes beyond the allocated defect-list buffer. Exploitation requires elevated execution against a defective or malicious SCSI device; 26.03.1 remains affected only on 32-bit builds.
The record
- CVE
- CVE-2026-10717
- Published
- Jun 2, 2026
- Updated
- Jun 2, 2026
- Vendor
- Seagate
- Product
- openSeaChest
- Classifications
- CWE-787, CAPEC-14, T1200
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 2, 2026CVE publishedPublication date reported by the CVE source.
- Jun 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=25.05.3
- Affected versionversion=26.03.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo