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