CVE-2023-45133 is an arbitrary code execution vulnerability in @babel/traverse prior to versions 7.23.2 and 8.0.0-alpha.4, as well as all versions of babel-traverse. When Babel compiles JavaScript that has been specifically crafted by an attacker, vulnerable evaluation logic reachable through the internal path.evaluate() or path.evaluateTruthy() methods can execute attacker-controlled code during the compilation process. The issue is exposed when plugins invoke those internal methods while analyzing untrusted source code. Known affected plugin paths include @babel/plugin-transform-runtime, @babel/preset-env when configured with useBuiltIns, and polyfill-provider plugins that depend on @babel/helper-define-polyfill-provider. The flaw affects build-time processing rather than runtime execution of already compiled application code.
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.
path.evaluate() or path.evaluateTruthy(), and disable or replace affected plugins until patched versions are deployed. Isolate build infrastructure, minimize privileges available to compilation jobs, and protect build secrets to reduce the impact of a compromise.Patch, then assume compromise.
@babel/traverse to version 7.23.2 or later, or to 8.0.0-alpha.4 or later on the 8.x alpha line. Where dependency resolution is managed through higher-level Babel packages, upgrading to @babel/core 7.23.2 or later will pull in a fixed @babel/traverse. If immediate upgrade of @babel/traverse is not possible, upgrade affected packages to versions that avoid the vulnerable code path, including @babel/plugin-transform-runtime 7.23.2, @babel/preset-env 7.23.2, @babel/helper-define-polyfill-provider 0.4.3, and corresponding updated polyfill-provider plugins. No security fix is indicated for Babel 6 babel-traverse.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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.