# CVE-2026-58303: Samsung Escargot stack-based buffer overflow in loop handling

Source: https://junglewise.ai/threats/cve-2026-58303-samsung-escargot-stack-based-buffer-overflow-in-loop-handling  
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-58303 · Severity: medium · CVSS 6.1 · Published 2026-07-09

Samsung Escargot, an open-source JavaScript engine often used in smart TVs and appliances, contains a memory management flaw. If a user is tricked into running a malicious script, the engine could crash or behave unpredictably, potentially impacting the stability of the device. This vulnerability primarily affects the availability of the service rather than the confidentiality of user data.

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

## Quick answers

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

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

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

**Is there a fix for CVE-2026-58303?** A patch was published on 2026-06-16: 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-58303 attacked?** It is attacked with local access, in a software library.

**Am I affected by CVE-2026-58303?** 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

A stack-based buffer overflow (CWE-121) exists in Samsung's Escargot JavaScript engine due to improper handling of labeled 'continue' statements within various loop structures (For, ForIn, ForOf, While, and DoWhile). The root cause involves a failure to correctly manage environment record unwinding and iterator cleanup when a labeled continue crosses allocated block boundaries. An attacker can exploit this by providing a specially crafted JavaScript file that triggers an environment record mismatch or improper stack state, leading to a crash (DoS) or potentially limited integrity impact. The vulnerability requires local execution or user interaction to run the malicious script. A fix has been merged into the master branch in commit b30b63fc63b403907d8137da1c65aaa4521fe74e.

## Affected products

- Samsung Escargot before b30b63fc63b403907d8137da1c65aaa4521fe74e

## Timeline

- 2026-06-15: other: Fix developed and submitted via pull request
- 2026-06-16: patched: Fix merged into master branch
- 2026-07-09: disclosed: CVE published to NVD

## References

- [https://github.com/Samsung/escargot/issues/1571](https://github.com/Samsung/escargot/issues/1571)
- [https://github.com/Samsung/escargot/pull/1585](https://github.com/Samsung/escargot/pull/1585)

## 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)