build(deps): bump js-yaml to 3.15.1/4.3.1 to clear GHSA-5p4m-2wfm-xmqj - #1204
Draft
cursor[bot] wants to merge 1 commit into
Draft
build(deps): bump js-yaml to 3.15.1/4.3.1 to clear GHSA-5p4m-2wfm-xmqj#1204cursor[bot] wants to merge 1 commit into
cursor[bot] wants to merge 1 commit into
Conversation
…xmqj js-yaml versions <3.15.1 and <4.3.1 have quadratic CPU consumption in !!omap resolution (GHSA-5p4m-2wfm-xmqj, high). Both versions are pulled in only as transitive dev deps (via @istanbuljs/load-nyc-config and eslint@8.57.1) and the newer patch releases satisfy the existing ^3.13.1 and ^4.1.0 ranges, so a lockfile refresh clears the advisory without any manifest or resolutions changes. Co-authored-by: Andreja Kogovsek <andrejak@users.noreply.github.com>
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
1 participant
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.
What
Refreshes the two transitive
js-yamlentries in the rootyarn.lockfrom3.15.0→3.15.1and4.3.0→4.3.1.Why
Both existing versions are flagged by the new advisory GHSA-5p4m-2wfm-xmqj (high — quadratic CPU consumption in
!!omapresolution, CVE-2026-59870). Fixed in3.15.1and4.3.1respectively.Both new versions satisfy the existing manifest ranges (
^3.13.1via@istanbuljs/load-nyc-config,^4.1.0viaeslint@8.57.1), so this is a pure lockfile refresh — nopackage.json, noresolutions, no runtime code touched. Only used by dev/test tooling; the shipped library is unaffected either way.How
Deleted the two
js-yamlblocks inyarn.lockand re-ranyarn install, which re-resolved them to the newest matching patch releases.yarn npm audit --recursive --all --jsonno longer reports GHSA-5p4m-2wfm-xmqj afterwards.Notes
Other open advisories on this repo (brace-expansion, fast-uri, ip-address, undici) are already covered by open PRs (#1200 – #1203) and are intentionally not touched here to keep this diff small and reviewable.