Quick answers
- Is CVE-2026-14160 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14160 being exploited in the wild.
- How severe is CVE-2026-14160?
- Medium severity, with a CVSS score of 5.9, published 30 June 2026.
- Which products and versions are affected?
- Samsung Escargot bab3a5797557014ce3c2e28419a6310cfba90d0d.
- Is there a fix for CVE-2026-14160?
- A patch was published on 2026-06-29: Fix committed to GitHub repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-14160 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-14160?
- 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 Time-of-check time-of-use (TOCTOU) race condition exists in Samsung's Escargot JavaScript engine. The vulnerability is rooted in the engine's failure to revalidate ArrayBuffer status and bounds after user-controlled code execution (such as valueOf coercion) during Atomics operations. An attacker can exploit this by detaching or resizing a buffer during the coercion phase, leading to out-of-bounds (OOB) access when the operation resumes. This local attack vector allows for potential information disclosure or integrity violations. A fix has been identified in commit 9e8084e which introduces the revalidateAtomicAccess helper to verify buffer state before memory access.
Affected products
- Samsung Escargot bab3a5797557014ce3c2e28419a6310cfba90d0d
Timeline
- 2026-06-30: advisory: NVD publication date
- 2026-06-29: patched: Fix committed to GitHub repository