Engine crash via stale finalizer source pointer
Published May 19, 2026 · Updated May 19, 2026
Invalid pointer release in Samsung Escargot 590345cc6258317c5da850d846ce6baaf2afc2d3 allows local users to crash the engine. FinalizationRegistryObject finalizers can retain a stale source pointer because garbage-collection finalizers are unordered, then access the collected registry through that invalid pointer. Exploitation requires user interaction with crafted JavaScript and interrupts only the affected engine process.
Summary
What happened
Invalid pointer release in Samsung Escargot 590345cc6258317c5da850d846ce6baaf2afc2d3 allows local users to crash the engine. FinalizationRegistryObject finalizers can retain a stale source pointer because garbage-collection finalizers are unordered, then access the collected registry through that invalid pointer. Exploitation requires user interaction with crafted JavaScript and interrupts only the affected engine process.
The record
- CVE
- CVE-2026-47312
- Published
- May 19, 2026
- Updated
- May 19, 2026
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Escargot
- Classifications
- CWE-763, CAPEC-123, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 19, 2026CVE publishedPublication date reported by the CVE source.
- May 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=590345cc6258317c5da850d846ce6baaf2afc2d3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo