Skip to content

fix(security): remediate js-yaml omap quadratic CPU DoS advisory (High) - #717

Open
fro-bot wants to merge 1 commit into
mainfrom
fro-bot/security-js-yaml-omap-dos
Open

fro-bot wants to merge 1 commit into
mainfrom
fro-bot/security-js-yaml-omap-dos

Conversation

@fro-bot

@fro-bot fro-bot commented Aug 8, 2026

Copy link
Copy Markdown
Collaborator

Summary

Remediates GHSA-5p4m-2wfm-xmqj (High) — quadratic CPU consumption in !!omap resolution affecting js-yaml 3.x and 4.x. This is the same weakness as CVE-2026-59870 (GHSA-724g-mxrg-4qvm), fixed upstream in the 5.x line at 5.2.1, but never backported to the 3.x/4.x legacy lines.

Change

Pins the transitive js-yaml dependency to ^5.2.1 via a pnpm-workspace.yaml override, following the same pattern as the existing fast-uri override. Resolved version: 5.2.3.

js-yaml is a dev-only transitive dependency here (pulled in by @eslint/eslintrc, jsdom, confbox, katex, toml-eslint-parser) — it only parses trusted local config/build-time YAML, not untrusted user input, but the fix is minimal and reversible so it's included per the security remediation scope.

Verification

All quality gates pass unchanged with the override applied:

  • pnpm lint — 0 errors (44 pre-existing warnings, unchanged)
  • pnpm exec tsc --noEmit — clean
  • pnpm test — 1298 passed / 57 files, 0 failed
  • pnpm build — tsc + vite build succeeded

Removal criteria

Remove this override once all transitive consumers (@eslint/eslintrc, jsdom, confbox, katex, toml-eslint-parser) bump their own js-yaml requirement past 5.2.1.


🤖 Generated by Fro Bot autohealing (schedule-95a0d398-31239756521).

Pin transitive js-yaml to ^5.2.1 via pnpm override to remediate
GHSA-5p4m-2wfm-xmqj (CVE-2026-59870 fix never backported to 3.x/4.x
lines). js-yaml is a dev-only transitive dependency (jsdom,
@eslint/eslintrc, confbox, katex, toml-eslint-parser); resolved
version is 5.2.3.

Verified lint (0 errors), tsc --noEmit, vitest (1298 passed), and
vite build all pass unchanged with the override applied.

This branch has not been deployed

No deployments
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