build(deps): force js-yaml >=4.2.0 to clear CVE-2026-53550#14
Merged
Conversation
@changesets/cli pulls js-yaml 3.14.2 transitively via read-yaml-file, which is vulnerable to a quadratic-complexity DoS (GHSA-h67p-54hq-rp68). No patched 3.x exists, so a scoped pnpm override (js-yaml@<4.2.0 -> ^4.2.0) forces the fixed 4.x line. read-yaml-file calls the removed safeLoad API, but 4.2.0 still ships a deprecation shim, so changesets keeps working — verified changeset status, build, and tests all pass.
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
Adds a scoped pnpm override forcing
js-yaml@<4.2.0→^4.2.0, eliminating the vulnerablejs-yaml@3.14.2from the dependency tree.Why
Dependabot alert #28 (GHSA-h67p-54hq-rp68 / CVE-2026-53550) — a quadratic-complexity DoS in js-yaml merge-key handling.
@changesets/clipulls injs-yaml@3.14.2transitively viaread-yaml-file@1.1.0, which pins the 3.x line.There is no patched 3.x release (only
4.2.0is fixed), andread-yaml-filecan't move to 4.x on its own, so a forced override is the only available fix.Why this is safe
read-yaml-filecalls thesafeLoadAPI, which was removed as a hard export in js-yaml 4.x — but4.2.0still ships a deprecation shim (module.exports.safeLoad = renamed('safeLoad', 'load')), so changesets keeps working.Verified:
pnpm changeset statusruns (loads config via the shim without error)pnpm build✅pnpm test— 35/35 ✅Notes
No changeset — this is a dev-only, transitive dependency and does not affect the published
dist/.Closes #28