Skip to content

[agent] chore(deps): bump js-yaml to 4.2.0#785

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
security/bump-js-yaml-4.2.0-3c5a17f89436b388
Draft

[agent] chore(deps): bump js-yaml to 4.2.0#785
github-actions[bot] wants to merge 1 commit into
mainfrom
security/bump-js-yaml-4.2.0-3c5a17f89436b388

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Addresses Dependabot alert #276GHSA-h67p-54hq-rp68 / CVE-2026-53550 (medium, CVSS 5.3): quadratic-complexity DoS in js-yaml merge-key handling via repeated aliases. All versions ≤ 4.1.1 are affected; patched in 4.2.0.

Changes

packages/mql-typescript/package.json

  • Bumped direct dependency js-yaml from ^4.1.1^4.2.0

package.json (root)

  • Added overrides.js-yaml: "^4.2.0" to force all transitive consumers to the patched version.

Why overrides were needed: Several direct dependencies in this monorepo (@eslint/eslintrc, eslint, lerna, mocha, mongodb-schema, @bcherny/json-schema-ref-parser) pin or resolve js-yaml to versions ≤ 4.1.1. None of them have shipped a release that pulls in 4.2.0 yet, so a manifest-level override is required to ensure the patched version is installed everywhere.

Result

After npm install, all js-yaml 4.x instances in package-lock.json resolve to 4.2.0. The js-yaml 3.x tree (used by packages that explicitly depend on ^3.x) is unaffected.

Generated by Dependabot remediation agent · ● 729.5K ·

- Bump direct dependency in packages/mql-typescript from ^4.1.1 to ^4.2.0
- Add root overrides to force all transitive js-yaml 4.x to ^4.2.0,
  covering @eslint/eslintrc, eslint, lerna, mocha, mongodb-schema, and
  @bcherny/json-schema-ref-parser which all resolved to <=4.1.1

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants