Skip to content

fix: upgrade js-yaml to 3.15.2 to resolve GHSA-2883-xcg3-v3hh - #1111

Merged
sonukapoor merged 1 commit into
mainfrom
bugfix/issue-1110-js-yaml-advisory
Sep 9, 2026
Merged

fix: upgrade js-yaml to 3.15.2 to resolve GHSA-2883-xcg3-v3hh#1111
sonukapoor merged 1 commit into
mainfrom
bugfix/issue-1110-js-yaml-advisory

Conversation

@sonukapoor

Copy link
Copy Markdown
Collaborator

A new advisory published a few hours ago turned Self Scan red on main.

GHSA-2883-xcg3-v3hh flags js-yaml below 3.15.2 for unbounded CPU use when
maxTotalMergeKeys encounters empty merge sources. We resolve 3.15.1, so the
scan reported one new finding above baseline and the ratchet gate exited 1.

The finding is dev-only and transitive, reached through jest via
@istanbuljs/load-nyc-config@1.1.0, which already allows 3.15.2 in its
existing range. Applied with cve-lite . --fix, which took it as a within-range
refresh, so package.json is untouched and no override or baseline entry was
needed.

Rescan afterwards reports no known vulnerabilities. Full suite is green at 1790
tests and the build is clean.

Closes #1110

A new advisory published 2026-09-08 flags js-yaml below 3.15.2 for
unbounded CPU use when maxTotalMergeKeys sees empty merge sources.

The finding is dev-only and transitive, reached through jest via
@istanbuljs/load-nyc-config@1.1.0, which already permits 3.15.2 inside
its existing range. Applied with cve-lite --fix as a within-range
refresh, so package.json is unchanged and no baseline entry is needed.
@sonukapoor
sonukapoor merged commit 7067626 into main Sep 9, 2026
6 checks passed
@sonukapoor
sonukapoor deleted the bugfix/issue-1110-js-yaml-advisory branch September 9, 2026 00:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Self Scan failing on main: new js-yaml advisory GHSA-2883-xcg3-v3hh

1 participant