Skip to content

Fix js-yaml security advisories in rush-lib - #5950

Closed
Jackson Weber (JacksonWeber) wants to merge 1 commit into
microsoft:mainfrom
JacksonWeber:jacksonweber-fix-rush-js-yaml
Closed

Fix js-yaml security advisories in rush-lib#5950
Jackson Weber (JacksonWeber) wants to merge 1 commit into
microsoft:mainfrom
JacksonWeber:jacksonweber-fix-rush-js-yaml

Conversation

@JacksonWeber

Copy link
Copy Markdown

Fixes #5843.

Summary

  • Upgrade the shared direct js-yaml dependency from ~4.1.0 to ~4.3.1, including @microsoft/rush-lib.
  • Refresh both PNPM subspace lockfiles and their Rush repository-state hashes.
  • Add the required Rush change file.

Security rationale

~4.2.0, as proposed by #5847, addresses GHSA-h67p-54hq-rp68 but is no longer a sufficient floor. CVE-2026-59869 is fixed in js-yaml 4.3.0, while GHSA-5p4m-2wfm-xmqj requires 4.3.1. Using ~4.3.1 addresses all three advisories while remaining within the existing major version.

Validation

  • rush check --subspace default
  • rush install --to @microsoft/rush-lib --bypass-policy
  • rush build --to @microsoft/rush-lib
  • Verified both generated lockfiles match their Rush pnpmShrinkwrapHash values and contain no js-yaml@4.1.1 resolution.

Raise the shared js-yaml dependency to ~4.3.1 and refresh Rush dependency metadata.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@github-project-automation github-project-automation Bot moved this to Needs triage in Bug Triage Aug 21, 2026
@github-project-automation github-project-automation Bot moved this from Needs triage to Closed in Bug Triage Aug 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Closed

Development

Successfully merging this pull request may close these issues.

[rush] @microsoft/rush-lib depends on a version of js-yaml that has a security issue

1 participant