Quick answers
- Is CVE-2026-92259 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92259 being exploited in the wild.
- How severe is CVE-2026-92259?
- Medium severity, with a CVSS score of 5.5, published 15 September 2026.
- Which products and versions are affected?
- Samsung Escargot commit ac94df78493ee6fede286620d94f724e46b4d238 and earlier.
- Is there a fix for CVE-2026-92259?
- A patch was published on 2026-08-24: Fix merged in pull request #1650 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92259 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-92259?
- 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 integer overflow or wraparound in Samsung Escargot's bytecode cache handling that leads to a heap-based buffer overflow. The attack requires write access to the bytecode-cache directory on the target system. When a crafted cache file is processed, the integer overflow occurs during cache validation or size calculation, causing a buffer overflow that results in denial of service (crash). The fix is available in commit ac94df78493ee6fede286620d94f724e46b4d238 and related patches merged in pull request #1650.
Affected products
- Samsung Escargot commit ac94df78493ee6fede286620d94f724e46b4d238 and earlier
Timeline
- 2026-09-15: disclosed
- 2026-08-24: patched: Fix merged in pull request #1650