# CVE-2026-47316: Samsung Escargot denial of service via improper exception handling

Source: https://junglewise.ai/threats/cve-2026-47316-samsung-escargot-denial-of-service-via-improper-exception  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-19. Updated: 2026-05-19  
License: CC BY 4.0 with a link back

CVE-2026-47316 · Severity: medium · CVSS 5.5 · Published 2026-05-19

Samsung Escargot, an open-source JavaScript engine often used in smart TVs and appliances, contains a vulnerability that can cause the engine to crash. By providing specifically crafted input data, an attacker could trigger an unhandled error condition that leads to a denial-of-service. This could result in application instability or the failure of services relying on the JavaScript engine.

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

## Quick answers

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

**How severe is CVE-2026-47316?** Medium severity, with a CVSS score of 5.5, published 19 May 2026.

**Which products and versions are affected?** Samsung Escargot 590345cc6258317c5da850d846ce6baaf2afc2d3.

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

**Am I affected by CVE-2026-47316?** 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 vulnerability classified as CWE-703 (Improper Check or Handling of Exceptional Conditions) exists in the Samsung Escargot JavaScript engine. The issue stems from a failure to properly validate pointers before dereferencing them, specifically in components like EscargotPublic.cpp, BuiltinTypedArray.cpp, and JSON.cpp. In certain edge cases, such as nested eval throws with finally allocations, an error value may be null; dereferencing this null pointer leads to a process crash. An attacker can exploit this by providing malicious JavaScript input that triggers these exceptional states. A fix has been identified in pull request #1565 which introduces necessary null checks.

## Affected products

- Samsung Escargot 590345cc6258317c5da850d846ce6baaf2afc2d3

## Timeline

- 2026-04-28: other: Fix pull request initiated on GitHub
- 2026-05-14: patched: Fix merged into master branch
- 2026-05-19: disclosed: CVE published by Samsung TV & Appliance

## References

- [https://github.com/Samsung/escargot/pull/1565](https://github.com/Samsung/escargot/pull/1565)

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