Update npm package js-yaml to v4.3.2 [SECURITY] - #9609
Open
hash-dependencies[bot] wants to merge 1 commit into
Open
Update npm package js-yaml to v4.3.2 [SECURITY]#9609hash-dependencies[bot] wants to merge 1 commit into
js-yaml to v4.3.2 [SECURITY]#9609hash-dependencies[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
PR SummaryLow Risk Overview There are no application or library code changes—only lockfile/package manifest updates after install. The upgrade addresses CVE-2026-84375 (YAML merge-key handling could burn CPU without respecting Reviewed by Cursor Bugbot for commit 3a841ef. Bugbot is set up for automated code reviews on this repo. Configure here. |
github-actions
Bot
added
area/deps
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 3a841ef. Configure here.
| "@changesets/assemble-release-plan@npm:^6.0.9": "patch:@changesets/assemble-release-plan@npm%3A6.0.9#~/.yarn/patches/@changesets-assemble-release-plan-npm-6.0.9-e01af97ef4.patch", | ||
| "@playwright/test": "1.58.2", | ||
| "@redocly/openapi-core/js-yaml": "4.3.1", | ||
| "@redocly/openapi-core/js-yaml": "4.3.2", |
There was a problem hiding this comment.
Lockfile still pins vulnerable js-yaml
High Severity
package.json now requests js-yaml 4.3.2, but yarn.lock still resolves every workspace and the package descriptor to 4.3.1. Yarn 4 installs from the lockfile, so CVE-2026-84375 remains unpatched in installed trees.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit 3a841ef. Configure here.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9609 +/- ##
=======================================
Coverage 65.93% 65.93%
=======================================
Files 1886 1886
Lines 198341 198341
Branches 8236 8236
=======================================
+ Hits 130772 130774 +2
+ Misses 66039 66037 -2
Partials 1530 1530 Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Merging this PR will not alter performance
|
| Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|
as_constant |
< 1 ns | < 1 ns | N/A | |
constant_equal |
< 1 ns | < 1 ns | N/A | |
constant_not_equal |
< 1 ns | < 1 ns | N/A | |
access |
< 1 ns | < 1 ns | N/A | |
runtime_equal |
< 1 ns | < 1 ns | N/A | |
runtime_not_equal |
< 1 ns | < 1 ns | N/A |
Comparing deps/js/npm-js-yaml-vulnerability (3a841ef) with main (94dff8e)1
Footnotes
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.
This PR contains the following updates:
4.3.1→4.3.2Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources
CVE-2026-84375 / GHSA-2883-xcg3-v3hh
More information
Details
Summary
maxTotalMergeKeysdoes not count empty mappings. An attacker can repeatedly merge a large sequence of them and consume significant CPU without reaching the configured limit.Example
For every target, the loader iterates all
Nelements ofarr. This results inO(N * K)work whiletotalMergeKeysremains unchanged.PoC
Observed results:
Impact
An attacker can submit a relatively small YAML document that causes prolonged CPU consumption despite the default
maxTotalMergeKeyslimit.Fix
Count each merge-source mapping as one budget unit, in addition to counting its keys.
Difference with v5
In v3 & v4, merge is enabled by default. So, the severity score is higher.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
nodeca/js-yaml (js-yaml)
v4.3.2Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate CLI.