Quick answers
- Is CVE-2026-25205 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-25205 being exploited in the wild.
- How severe is CVE-2026-25205?
- High severity, with a CVSS score of 7.4, published 13 April 2026.
- Which products and versions are affected?
- Samsung Escargot commit 97e8115ab1110bc502b4b5e4a0c689a71520d335.
- Is there a fix for CVE-2026-25205?
- A patch was published on 2026-04-08: Fix merged via GitHub Pull Request #1554 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-25205 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-25205?
- Check whether you run Samsung Escargot. 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 heap-based buffer overflow (CWE-122) exists in Samsung's Escargot JavaScript engine at commit 97e8115. The vulnerability allows for an out-of-bounds write, which can be leveraged by an attacker to corrupt memory. According to the vendor's CVSS assessment, the attack vector is local with high complexity, suggesting specific conditions or local access are required to trigger the overflow. Successful exploitation could lead to arbitrary code execution or a denial-of-service condition. A fix appears to have been addressed in pull request #1554 on the project's GitHub repository.
Affected products
- Samsung Escargot commit 97e8115ab1110bc502b4b5e4a0c689a71520d335
Timeline
- 2026-04-08: patched: Fix merged via GitHub Pull Request #1554
- 2026-04-13: advisory: Initial advisory published by Samsung
- 2026-04-13: disclosed: CVE-2026-25205 assigned