CVE-2026-59869 js-yaml: YAML merge-key chains can force quadratic CPU consumption - #1100
Merged
vharseko merged 1 commit intoAug 6, 2026
Conversation
… consumption Raise the js-yaml override in openam-ui-api from ^4.2.0 to ^4.3.0, resolving to 4.3.1. The override is what pinned the vulnerable version: grunt requires ~3.14.0, so without it npm falls back to the 3.x line. Completes OpenIdentityPlatform#1074, which fixed only openam-ui-ria.
vharseko
added
dependencies
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.
Bumps
js-yamlfrom 4.2.0 to 4.3.1 inopenam-ui-api(GHSA-52cp-r559-cp3m / CVE-2026-59869, patched in 4.3.0).Unlike the other recent dependency fixes this one needs a
package.jsonchange:grunt@1.6.2requires~3.14.0, so the version is governed by the existingoverridesentry — and that entry ("js-yaml": "^4.2.0") is exactly what pinned the package inside the vulnerable>=4.0.0 <4.3.0range. Raising it to^4.3.0resolves to 4.3.1.Completes #1074, which applied the same fix to
openam-ui-riaonly.js-yamlis a dev-scope transitive dependency of the UI build toolchain — it does not ship in the WAR.Verified:
integrityhash matchesnpm view js-yaml@4.3.1 dist.integritynpm install --package-lock-only --prefer-onlineis a no-op, so the build will not roll the version backnpm auditno longer reportsjs-yamlfor this modulegrunt.file.readYAML(which relies on thesafeLoadremoved in js-yaml 4) is not affected either way —openam-ui-api/Gruntfile.jsdoes not read YAML at all