Process crash via WebCrypto AES length overflow
Published Jun 26, 2026 · Updated Jun 26, 2026
Integer overflow in Node.js WebCrypto 22 before 22.23.0, 24 before 24.17.0, and 26 before 26.3.1 allows remote attackers to crash the process. The subtle.encrypt() AES path fails to reject an output length computed from an input whose size is a multiple of 2 GiB, causing integer overflow and process abort. Exploitation requires an application to pass attacker-controlled data of that size to WebCrypto; the bounded consequence is interruption of that Node.js process.
Summary
What happened
Integer overflow in Node.js WebCrypto 22 before 22.23.0, 24 before 24.17.0, and 26 before 26.3.1 allows remote attackers to crash the process. The subtle.encrypt() AES path fails to reject an output length computed from an input whose size is a multiple of 2 GiB, causing integer overflow and process abort. Exploitation requires an application to pass attacker-controlled data of that size to WebCrypto; the bounded consequence is interruption of that Node.js process.
The record
- CVE
- CVE-2026-48933
- Published
- Jun 26, 2026
- Updated
- Jun 26, 2026
- Vendor
- Node.js
- Product
- Node.js
- Classifications
- CWE-190, CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 26, 2026CVE publishedPublication date reported by the CVE source.
- Jun 26, 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=22.22.3 <=22.22.3
- Affected versionversion=24.16.0 <=24.16.0
- Affected versionversion=26.3.0 <=26.3.0
What conditions does exploitation require?
What is affected?
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