Repository navigation
fix(deps): patch js-yaml merge-source denial of service - #2384
Open
berkay-byte wants to merge 1 commit into
Open
berkay-byte wants to merge 1 commit into
berkay-byte wants to merge 1 commit into
Conversation
This branch has not been deployed
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
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.
Fixes #2358.
js-yaml@3.14.2is affected by CVE-2026-84375 / GHSA-2883-xcg3-v3hh: empty YAML merge sources bypass the merge-key budget and can exhaust CPU. Raise the direct devDependency floor to^3.15.2and update both npm lockfiles to the patched 3.x release. This also updates the copy shared with the Jest/Babel toolchain without a major-version migration.Add regression coverage that rejects empty merge sources exceeding a small budget and accepts ordinary merges within the budget. Exposure here is in development/spec-generation tooling; this PR does not claim a reachable production exploit.
Validation on Windows / Node 24:
npm ci --ignore-scriptssucceeded; installed js-yaml is 3.15.2.tsc -p core/tsconfig.json --noEmit).pmxt-ensure-server.test.tsexcluded. The full run otherwise passes after local LF normalization; that launcher test assumes Unix HOME/PATH and executable-script behavior and fails on Windows.generated/src/index.jsclient is absent in a fresh clone. The local environment has no Java runtime for OpenAPI generation.Other npm audit findings remain outside this focused fix. Full Linux/integration verification is still needed before merge.
Advisory: GHSA-2883-xcg3-v3hh