Skip to content

fix(deps): bump js-yaml to 4.3.2 (GHSA-2883-xcg3-v3hh) - #6161

Open
jaideepp247 wants to merge 1 commit into
Unitech:developmentfrom
jaideepp247:fix/js-yaml-cve-ghsa-2883
Open

jaideepp247 wants to merge 1 commit into
Unitech:developmentfrom
jaideepp247:fix/js-yaml-cve-ghsa-2883

Conversation

@jaideepp247

Copy link
Copy Markdown

Fixes #6158

js-yaml is pinned to 4.3.1, which falls in the range covered by GHSA-2883-xcg3-v3hh (high severity): maxTotalMergeKeys does not limit CPU use for empty merge sources. The advisory's first patched release is 4.3.2.

The published pm2@7.0.4 pins js-yaml at exactly 4.3.1 rather than a semver range, so installs resolve to the affected version and won't pick up 4.3.2 through a normal update.

This bumps the pin to 4.3.2 — a patch release within the same major, so there's no API change. PM2 calls yaml.load() in lib/Common.js; that signature and behaviour are unchanged.

Opened against development per CONTRIBUTING.md — happy to retarget to master, or to take 5.4.1 instead if you'd prefer the major bump.

@CLAassistant

CLAassistant commented Sep 17, 2026 •

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

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.

2 participants