Skip to content
← Reporting

vulnerabilityhighCVSS 7.5EPSS 0.39%

GHSA-2883-xcg3-v3hh: js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources

Source: github.com

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. Example ``yaml arr: &arr [{}, {}, {}, ...] N empty mappings targets: - <<: *arr repeated K times ` For every target, the loader iterates all N elements of arr. This results in O(N * K) work while totalMergeKeys remains unchanged. PoC ``js import { performance } from 'node:perf_hooks' import { load, YAML11_SCHEMA } from 'js-yaml' const n = 20000 const src = 'arr: &arr [' + '{},'.repeat(n).

Signalsas the pipeline stamped them

High High-risk vulnerability — CVSS 7.5

CVEKEV and EPSS where known

CVE-2026-84375not KEVEPSS 0.54%NVD →

Get the next one first

Every story goes to Telegram and RSS the moment it is published, and the whole wire is a keyless JSON API.

Telegram ↗KEV RSSAPIStack check