Memory corruption via reentrant promise rejection handling
Published Oct 16, 2025 · Updated Oct 16, 2025
Use-after-free in QuickJS 2025-04-26 allows attackers to corrupt process memory by supplying a crafted rejected promise. While js_std_promise_rejection_check dumps an Error reason, a custom getter can attach catch() to the same promise, freeing the current list entry during iteration. Execution of attacker-controlled JavaScript with a crafted Error getter is required; continued traversal then dereferences the freed entry, enabling process memory corruption or a crash.
Summary
What happened
Use-after-free in QuickJS 2025-04-26 allows attackers to corrupt process memory by supplying a crafted rejected promise. While js_std_promise_rejection_check dumps an Error reason, a custom getter can attach catch() to the same promise, freeing the current list entry during iteration. Execution of attacker-controlled JavaScript with a crafted Error getter is required; continued traversal then dereferences the freed entry, enabling process memory corruption or a crash.
The record
- CVE
- CVE-2025-62491
- Published
- Oct 16, 2025
- Updated
- Oct 16, 2025
- Vendor
- Fabrice Bellard
- Product
- QuickJS
- Classifications
- CWE-416
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2025CVE publishedPublication date reported by the CVE source.
- Oct 16, 2025Record 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=2025-04-26 <2025-09-13
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