Advisory Database
  • Advisories
  • Dependency Scanning
  1. npm
  2. ›
  3. js-yaml
  4. ›
  5. GHSA-r3ph-w7gj-g6xm

GHSA-r3ph-w7gj-g6xm: js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources

September 29, 2026

maxTotalMergeKeys does not count empty mappings. An attacker can repeatedly merge a large sequence of them and consume significant CPU without reaching the configured limit.

References

  • github.com/advisories/GHSA-r3ph-w7gj-g6xm
  • github.com/nodeca/js-yaml/commit/6a8e05f9a485188ed730ac81e81ae221352ef480
  • github.com/nodeca/js-yaml/releases/tag/5.4.1
  • github.com/nodeca/js-yaml/security/advisories/GHSA-r3ph-w7gj-g6xm

Code Behaviors & Features

Detect and mitigate GHSA-r3ph-w7gj-g6xm with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions starting from 5.0.0 before 5.4.1

Fixed versions

  • 5.4.1

Solution

Upgrade to version 5.4.1 or above.

Impact 5.3 MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Learn more about CVSS

Weakness

  • CWE-400: Uncontrolled Resource Consumption
  • CWE-407: Inefficient Algorithmic Complexity

Source file

npm/js-yaml/GHSA-r3ph-w7gj-g6xm.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Mon, 12 Oct 2026 00:22:22 +0000.