build(deps): Upgrade js-yaml 3.x to 3.14.2 to fix GHSA-mh29-5h37-fv8m#208
Merged
build(deps): Upgrade js-yaml 3.x to 3.14.2 to fix GHSA-mh29-5h37-fv8m#208
Conversation
The vulnerability is in js-yaml <3.14.2 (3.x branch). The instance in this repo comes via: jest → babel-plugin-istanbul → @istanbuljs/load-nyc-config → js-yaml@^3.13.1. There is no "bump dependants" path: @istanbuljs/[email protected] (latest) still requires js-yaml@^3.13.1, and [email protected] still uses @istanbuljs/load-nyc-config@^1.0.0. Since ^3.13.1 naturally satisfies 3.14.2, no resolutions override is needed — removing the stale lockfile entry is sufficient for yarn to re-resolve to the latest patched release. No package.json changes. Co-Authored-By: Claude <[email protected]>
HazAT
approved these changes
Feb 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrades the js-yaml 3.x lockfile entry from 3.14.1 to 3.14.2 to fix GHSA-mh29-5h37-fv8m (arbitrary code execution via untrusted YAML input).
The vulnerable instance comes via:
jest→babel-plugin-istanbul→@istanbuljs/load-nyc-config→js-yaml@^3.13.1. There is no "bump dependants" path —@istanbuljs/[email protected](latest) still pinsjs-yaml@^3.13.1, and[email protected]still pulls that same version in.Because the range
^3.13.1naturally satisfies 3.14.2, noresolutionsoverride is needed. Removing the stale lockfile entry is enough for yarn to re-resolve to the patched release. Onlyyarn.lockchanges —package.jsonis untouched.The separate
js-yaml@^4.1.0entry (used by eslint) is unaffected; GHSA-mh29-5h37-fv8m is specific to the 3.x branch.