# CVE-2026-58304: Samsung Escargot out-of-bounds read and write in ArrayBuffer

Source: https://junglewise.ai/threats/cve-2026-58304-samsung-escargot-out-of-bounds-read-and-write-in-arraybuffer  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-09. Updated: 2026-07-09  
License: CC BY 4.0 with a link back

CVE-2026-58304 · Severity: medium · CVSS 6.1 · Published 2026-07-09

Samsung Escargot is an open-source JavaScript engine used in various Samsung products like smart TVs and appliances. A vulnerability in how the engine handles memory buffers could allow a malicious script to read or write data outside of its intended boundaries. This could lead to application crashes or potentially allow an attacker to manipulate sensitive data within the device's memory.

Technologies: [Samsung Escargot](https://junglewise.ai/threats/technologies/escargot). Vendors: [Samsung](https://junglewise.ai/threats/vendors/samsung).

## Quick answers

**Is CVE-2026-58304 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-58304 being exploited in the wild.

**How severe is CVE-2026-58304?** Medium severity, with a CVSS score of 6.1, published 9 July 2026.

**Which products and versions are affected?** Samsung Escargot before 779f6bedf58f334dec64b0a51ebb724b4708b84a.

**Is there a fix for CVE-2026-58304?** A patch was published on 2026-05-27: Fix merged into master branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-58304 attacked?** It is attacked with local access, in a software library.

**Am I affected by CVE-2026-58304?** Check whether you run Samsung Escargot 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) read and write vulnerability exists in the Samsung Escargot JavaScript engine within the ArrayBuffer.prototype.transfer implementation. The root cause is a failure to validate that the 'newByteLength' parameter is less than or equal to the 'maxByteLength' of the buffer, leading to an assertion failure in debug builds and OOB memory access in release builds. An attacker can exploit this by providing a crafted length to the transfer method, potentially achieving arbitrary memory corruption or information disclosure within the context of the JavaScript runtime. The issue was addressed by adding proper bounds checking and throwing a RangeError when the requested length exceeds the original buffer's capacity.

## Affected products

- Samsung Escargot before 779f6bedf58f334dec64b0a51ebb724b4708b84a

## Timeline

- 2026-05-12: disclosed: Issue reported on GitHub
- 2026-05-27: patched: Fix merged into master branch
- 2026-07-09: advisory: CVE published to NVD

## References

- [https://github.com/Samsung/escargot/issues/1573](https://github.com/Samsung/escargot/issues/1573)
- [https://github.com/Samsung/escargot/pull/1580](https://github.com/Samsung/escargot/pull/1580)

## Related threats

- [Samsung Escargot use-after-free in string buffer access](https://junglewise.ai/threats/cve-2026-124684-use-after-free-vulnerability-in-samsung-open-source-escargot)
- [Samsung escargot out-of-bounds write in code cache](https://junglewise.ai/threats/cve-2026-118435-out-of-bounds-write-vulnerability-in-samsung-open-source)
- [Samsung Escargot integer overflow in bytecode cache](https://junglewise.ai/threats/cve-2026-92259-samsung-escargot-integer-overflow-in-bytecode-cache)
- [Samsung Escargot out-of-bounds write in class initialization](https://junglewise.ai/threats/cve-2026-86315-samsung-escargot-out-of-bounds-write-in-class-initialization)
- [Samsung Escargot out-of-bounds read and reachable assertion](https://junglewise.ai/threats/cve-2026-58307-samsung-escargot-out-of-bounds-read-and-reachable-assertion)