Skip to main content
Mallory
Unrated

Integer Overflow DoS in Node.js WebCrypto subtle.encrypt()

IdentifiersCVE-2026-48933CWE-190

CVE-2026-48933 is a high-severity vulnerability in the Node.js WebCrypto API affecting the 22.x, 24.x, and 26.x release lines. The flaw is described as an integer overflow in the WebCrypto implementation, specifically triggered when input passed to subtle.encrypt() is a multiple of 2 GiB. The issue has been characterized in reporting as affecting WebCrypto AES operations. When the vulnerable code processes such oversized input, the integer overflow can destabilize the Node.js process and cause it to terminate unexpectedly.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can crash the Node.js process, resulting in denial of service for the affected application or service. In remotely reachable applications that expose functionality using the vulnerable WebCrypto encrypt path, an attacker may be able to repeatedly trigger process termination and sustain service disruption.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by preventing untrusted remote users from supplying arbitrarily large inputs to code paths that invoke WebCrypto subtle.encrypt(). Enforce strict input size limits well below 2 GiB, validate and reject oversized payloads before encryption, and place network-facing services behind request-size and resource-consumption controls to reduce the likelihood of process-crash abuse. These are temporary mitigations and do not replace upgrading.

Remediation

Patch, then assume compromise.

Upgrade Node.js to a fixed supported release. The provided content identifies patched versions as Node.js v22.23.0 / v22.23.1, v24.17.0 / v24.17.1, and v26.3.1 / v26.3.2, depending on the source cited. Use the latest vendor-supported patched release available for the affected major line. End-of-life Node.js versions should not be used in production, as they remain vulnerable and unsupported.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6

Community discussion across Reddit, Mastodon, and other social sources.