Babel plugin transform ES2015 modules to CommonJS enables developers to seamlessly convert modern JavaScript ES2015 module syntax into the widely supported CommonJS format. This allows code written using import and export statements to run flawlessly in environments that primarily use require and module.exports, such as Node.js. Version 6.26.0, released in August 2017, builds upon the solid foundation of version 6.24.1 from April 2017 with a few key updates.
The most notable difference lies in the updated dependencies. Version 6.26.0 upgrades babel-runtime, babel-template, and babel-types to version 6.26.0, bringing in the latest bug fixes and potential performance improvements associated with those core Babel packages. Additionally, it introduces a new development dependency, babel-plugin-syntax-object-rest-spread version 6.13.0. While seemingly minor, this dependency might be relevant for developers using object rest and spread syntax during development or testing, ensuring correct parsing and handling within the plugin's test environment.
For developers selecting between these versions, the choice depends on their specific needs. If already deeply integrated with a specific Babel ecosystem and closely tracking minor releases for bug fixes, version 6.26.0 provides a seamless upgrade path to maintain compatibility and benefit from the latest improvements in the Babel ecosystem. Otherwise, version 6.24.1 offers a stable and reliable alternative, particularly for projects prioritizing stability and minimal dependency upgrades. Both versions effectively address the core purpose of the plugin: bridging the gap between modern JavaScript module syntax and CommonJS environments.
All the vulnerabilities related to the version 6.26.0 of the package
Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code
Using Babel to compile code that was specifically crafted by an attacker can lead to arbitrary code execution during compilation, when using plugins that rely on the path.evaluate()or path.evaluateTruthy() internal Babel methods.
Known affected plugins are:
@babel/plugin-transform-runtime@babel/preset-env when using its useBuiltIns option@babel/helper-define-polyfill-provider, such as babel-plugin-polyfill-corejs3, babel-plugin-polyfill-corejs2, babel-plugin-polyfill-es-shims, babel-plugin-polyfill-regeneratorNo other plugins under the @babel/ namespace are impacted, but third-party plugins might be.
Users that only compile trusted code are not impacted.
The vulnerability has been fixed in @babel/traverse@7.23.2.
Babel 6 does not receive security fixes anymore (see Babel's security policy), hence there is no patch planned for babel-traverse@6.
@babel/traverse to v7.23.2 or higher. You can do this by deleting it from your package manager's lockfile and re-installing the dependencies. @babel/core >=7.23.2 will automatically pull in a non-vulnerable version.@babel/traverse and are using one of the affected packages mentioned above, upgrade them to their latest version to avoid triggering the vulnerable code path in affected @babel/traverse versions:
@babel/plugin-transform-runtime v7.23.2@babel/preset-env v7.23.2@babel/helper-define-polyfill-provider v0.4.3babel-plugin-polyfill-corejs2 v0.4.6babel-plugin-polyfill-corejs3 v0.8.5babel-plugin-polyfill-es-shims v0.10.0babel-plugin-polyfill-regenerator v0.5.3