Skip to content

chore(security): bump js-yaml to >=4.3.0 (GHSA-52cp-r559-cp3m, alert #722)#34480

Open
Alyar666 wants to merge 1 commit into
DevExpress:mainfrom
Alyar666:sec-jsyaml-main
Open

chore(security): bump js-yaml to >=4.3.0 (GHSA-52cp-r559-cp3m, alert #722)#34480
Alyar666 wants to merge 1 commit into
DevExpress:mainfrom
Alyar666:sec-jsyaml-main

Conversation

@Alyar666

@Alyar666 Alyar666 commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

No description provided.

The existing override capped js-yaml at ^4.2.0, which still resolves to
the vulnerable 4.2.0. GHSA-52cp-r559-cp3m / CVE-2026-59869 (high) is a
quadratic-CPU DoS via YAML merge-key chains, patched in 4.3.0. js-yaml
is a transitive dev/build dependency only and is not shipped in any
published package. Fixes Dependabot alert DevExpress#722.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the pnpm dependency override to ensure js-yaml resolves to a non-vulnerable version (>= 4.3.0), addressing Dependabot alert #722 for GHSA-52cp-r559-cp3m / CVE-2026-59869. This change is applied at the workspace/lockfile level and primarily affects dev/build-time dependency resolution.

Changes:

  • Updated pnpm-workspace.yaml override rule to force js-yaml@<4.3.0 to resolve to ^4.3.0.
  • Updated pnpm-lock.yaml to reflect the new override and resolved js-yaml version 4.3.0 across affected snapshots.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File Description
pnpm-workspace.yaml Adjusts the workspace override so vulnerable js-yaml versions resolve to ^4.3.0.
pnpm-lock.yaml Updates lockfile override and resolution entries to js-yaml@4.3.0.
Files not reviewed (1)
  • pnpm-lock.yaml: Generated file

@Alyar666
Alyar666 added this pull request to the merge queue Jul 24, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants