CVE-2026-118435: Samsung escargot out-of-bounds write in code cache

CVE-2026-118435 · Severity: medium · CVSS 5.4 · Published 2026-10-28

Samsung escargot is a JavaScript engine used in embedded and IoT devices. An out-of-bounds write vulnerability in its code cache writer can allow an attacker to corrupt memory and potentially execute arbitrary code. The issue arises from incorrect buffer reservation when handling tagged templates, leading to buffer manipulation and possible crashes or code execution.

Technologies: Samsung Escargot. Vendors: Samsung.

Quick answers

Is CVE-2026-118435 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-118435 being exploited in the wild.
How severe is CVE-2026-118435?
Medium severity, with a CVSS score of 5.4, published 28 October 2026.
Which products and versions are affected?
Samsung Escargot versions prior to fix commit 89da0fb.
Is there a fix for CVE-2026-118435?
A patch was published on 2026-10-26: Fix merged in pull request #1750 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-118435 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-118435?
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

The vulnerability is an out-of-bounds write in escargot's code cache writer that fails to reserve sufficient buffer space for block identifiers and bytecode flags—reserving room for two booleans but writing three. Additionally, chained tagged templates cause exponential AST traversal, revisiting nodes through both original and converted call paths. An attacker can craft malicious JavaScript with tagged templates to trigger memory corruption during code cache serialization.

Affected products

  • Samsung escargot versions prior to fix commit 89da0fb

Timeline

  • 2026-10-28: disclosed
  • 2026-10-26: patched: Fix merged in pull request #1750

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.