The @babel/runtime package provides modular runtime helpers for Babel, facilitating the execution of transformed code in environments where these helpers are not natively available. Version 7.0.0 represents a significant milestone, marking a shift towards greater stability and compatibility. Compared to its prior iterations (the data of which is unfortunately not available), developers can expect improvements in terms of performance and reduced bundle sizes thanks to potential code optimizations and dependency updates. Version 7.0.0 depends on regenerator-runtime version "^0.12.0", which suggests a focus on supporting async/await functionality.
This version, released on August 27, 2018, under the MIT license, emphasizes ease of integration and aligns with Babel's core philosophy of enabling modern JavaScript features across diverse platforms. The package's presence on GitHub (https://github.com/babel/babel/tree/master/packages/babel-runtime) guarantees transparency and community contribution. Developers choosing @babel/runtime@7.0.0 can leverage a well-maintained, modular solution to resolve common runtime dependencies, thus streamlining their build processes and ensuring cross-browser compatibility for their Babel-transformed code, especially as it relates to features like generators and asynchronous programming. The unpacked size of 51113 bytes across 130 files suggests a reasonably lightweight footprint within a project's dependencies.
All the vulnerabilities related to the version 7.0.0 of the package
Babel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groups
When using Babel to compile regular expression named capturing groups, Babel will generate a polyfill for the .replace method that has quadratic complexity on some specific replacement pattern strings (i.e. the second argument passed to .replace).
Your generated code is vulnerable if all the following conditions are true:
.replace method on a regular expression that contains named capturing groups.replaceIf you are using @babel/preset-env with the targets option, the transform that injects the vulnerable code is automatically enabled if:
You can verify what transforms @babel/preset-env is using by enabling the debug option.
This problem has been fixed in @babel/helpers and @babel/runtime 7.26.10 and 8.0.0-alpha.17, please upgrade. It's likely that you do not directly depend on @babel/helpers, and instead you depend on @babel/core (which itself depends on @babel/helpers). Upgrading to @babel/core 7.26.10 is not required, but it guarantees that you are on a new enough @babel/helpers version.
Please note that just updating your Babel dependencies is not enough: you will also need to re-compile your code.
If you are passing user-provided strings as the second argument of .replace on regular expressions that contain named capturing groups, validate the input and make sure it does not contain the substring $< if it's then not followed by > (possibly with other characters in between).
This vulnerability was reported and fixed in https://github.com/babel/babel/pull/17173.