Skip to content

Bump js-yaml to 4.3.0 - #27

Merged
scsmith merged 1 commit into
mainfrom
fix-js-yaml-dos
Jul 30, 2026
Merged

Bump js-yaml to 4.3.0#27
scsmith merged 1 commit into
mainfrom
fix-js-yaml-dos

Conversation

@scsmith

@scsmith scsmith commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Fixes dependabot alert #82 (GHSA-52cp-r559-cp3m / CVE-2026-59869) — js-yaml < 4.3.0 can burn quadratic CPU on chained YAML merge keys. Transitive dev dependency via eslint; lockfile-only change, no package.json bump needed.

Fixes GHSA-52cp-r559-cp3m / CVE-2026-59869 (quadratic CPU on chained
YAML merge keys), dependabot alert #82. Dev-only dependency.
@scsmith
scsmith merged commit 7b5b322 into main Jul 30, 2026
6 checks passed
@scsmith
scsmith deleted the fix-js-yaml-dos branch July 30, 2026 13:57
scsmith added a commit that referenced this pull request Aug 17, 2026
…5p4m-2wfm-xmqj]

Quadratic CPU consumption in !!omap resolution, affecting both the 3.x and
4.x lines. #27 bumped to 4.3.0 the day before 4.3.1 shipped, so this picks up
the tail of that plus the nested 3.x copy under @istanbuljs/load-nyc-config.

Both are devDependencies (eslint and jest), so nothing reaches consumers of
the published package. Lockfile-only, within the existing ranges.

npm audit goes from 1 high to 0.
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.

1 participant