Yup version 0.26.7 arrives as a subtle refinement over its predecessor, version 0.26.6, offering developers a dependable schema validation solution. Both versions maintain the core functionality of dead simple object schema validation, powered by key dependencies such as Lodash, fn-name, toposort, property-expr, @babel/runtime, and synchronous-promise for a robust foundation. The development dependencies remain consistent across both versions, featuring tools like Chai, Jest, Husky, and Rollup, ensuring a stable testing and building environment.
While the feature set remains consistent between the two versions, a notable difference lies in the unpacked size and release date. Version 0.26.7 slightly increases to 130931 from 129368, suggesting minor additions or refactoring which doesn't drastically impact the library's footprint. Released on January 10, 2019, it comes several months after version 0.26.6, released on September 19, 2018; this time difference may point to bug fixes, performance improvements, or dependency updates addressed between releases. For developers, this indicates a commitment to ongoing maintenance and improvement of the library. While the specific changes aren't explicitly highlighted, the updated release suggests staying current as a best practice, ensuring you benefit from any refinements made to the validation process. Both versions are licensed under MIT, making them freely usable in a variety of projects.
All the vulnerabilities related to the version 0.26.7 of the package
Prototype Pollution in property-expr
The package property-expr before 2.0.3 are vulnerable to Prototype Pollution via the setter function.
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.