CVE-2026-44728
HIGHCVE-2026-44728 is a high-severity (CVSS 8.2) remote code execution vulnerability in @babel/plugin-transform-modules-systemjs. O3 Security confirms whether CVE-2026-44728 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Improper Control of Generation of Code when compiling specifically crafted malicious code with @babel/plugin-transform-modules-systemjs
Real-World Exposure
@babel/plugin-transform-modules-systemjs📦@babel/plugin-transform-modules-systemjsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
Babel is a compiler for writing next generation JavaScript. From 7.12.0 to before 7.29.4 and 8.0.0-alpha.13, using Babel to compile code that was specifically crafted by an attacker can cause Babel to generate output code that executes arbitrary code. This vulnerability is fixed in 7.29.4 and 8.0.0-alpha.13.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @babel/plugin-transform-modules-systemjs | ≥ 7.12.0&&< 7.29.4 | 7.29.4 |
| 📦npm | @babel/plugin-transform-modules-systemjs | ≥ 8.0.0-alpha.0&&< 8.0.0-alpha.13 | 8.0.0-alpha.13 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @babel/plugin-transform-modules-systemjs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @babel/plugin-transform-modules-systemjs to 7.29.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44728 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-44728 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-44728. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-44728 in your dependencies?
O3 detects CVE-2026-44728 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.