Repository navigation
fix(deps): bump js-yaml to 4.2.0 (CVE-2026-53550) - #1035
Merged
Merged
Conversation
Changyong Gong (chagong)
requested review from
Jinbo Wang (testforstephen) and
wenyt (wenytang-ms)
as code owners
June 23, 2026 02:42
wenyt (wenytang-ms)
approved these changes
Jun 23, 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
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.
Fixes Dependabot alert #94.
Vulnerability
js-yaml(npm, dev dependency, transitive viacosmiconfig)<<) handling via repeated aliases. A crafted YAML document can cause CPU exhaustion when parsed.<= 4.1.14.2.0Change
Bumped
js-yaml4.1.1→4.2.0inpackage-lock.json(npm update js-yaml).4.2.0satisfies the existing^4.1.0constraint, so only the lockfile changed.