Loading vulnerability…
CVE-2023-32002 is a vulnerability in Node.js in which use of the internal Module._load() mechanism can bypass the experimental policy enforcement mechanism and load modules that are not permitted by the application's policy.json definition. The issue affects active Node.js release lines 16.x, 18.x, and 20.x at the time of disclosure when the experimental policy feature is in use. By circumventing policy restrictions intended to constrain module loading, the flaw can undermine trust boundaries established by the policy system and enable execution of code through unauthorized module imports.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Node.js Module._load() policy remote code execution vulnerability listed as affecting Visual Studio and CBL Mariner in this release context.
A high-severity remote code execution vulnerability in Microsoft Visual Studio 2019 mentioned as part of the broader February 2025 Microsoft patch set.
A remote code execution vulnerability related to Node.js `Module._load()` policy handling.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.