CVE-2026-47683 patriksimek CVE debrief

Who should care

Defenders responsible for systems using vm2 for sandboxing Node.js applications should assess the potential impact of this vulnerability and prioritize verification and remediation efforts.

Why it matters

CVE-2026-47683 is a high-severity vulnerability in vm2 that allows sandbox code to bypass the bufferAllocLimit cap, potentially exhausting the host process. Defenders should prioritize verifying exposure and assessing the impact on systems using vm2 for sandboxing Node.js applications.

• Defenders should verify exposure and assess the impact on systems using vm2 for sandboxing Node.js applications.
• The vulnerability allows sandbox code to perform large synchronous host external-memory allocations that bypass the configured cap and can exhaust the host process.
• Remediation priority follows from verifying exposure and assessing the impact, with a focus on updating to version 3.11.6 or later.

Technical summary

The bufferAllocLimit enforcement in lib/setup-sandbox.js does not cover Buffer.concat(list, totalLength) or Buffer.from(arrayLike) with an attacker-controlled length, allowing sandbox code to perform large synchronous host external-memory allocations that bypass the configured cap and can exhaust the host process. This issue allows defenders to prioritize verifying exposure and assessing the impact on systems using vm2 for sandboxing Node.js applications, with a focus on updating to version 3.11.6 or later. The vulnerability enables sandbox code to perform large synchronous host external-memory allocations that bypass the configured cap and can exhaust the host process, emphasizing the need for defenders to act

Defensive priority

Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, especially those using vm2 for sandboxing Node.js applications.

Recommended defensive actions

• Verify if the system uses vm2 for sandboxing Node.js applications and assess the potential impact of this vulnerability.
• Check if the version of vm2 is prior to 3.11.6 and update to 3.11.6 or later if necessary.
• Monitor system resources for signs of exhaustion due to large synchronous host external-memory allocations.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its impact, and the fixed version. However, the corpus does not establish versions, exploitation, impact, or remediation beyond the provided information, requiring verification from the supplied official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.