yaml is vulnerable to Stack Overflow via deeply nested YAML collections

Summary

`yaml` is a YAML parser and serialiser for JavaScript. Parsing a YAML document with a version of `yaml` on the 1.x branch prior to 1.10.3 or on the 2.x branch prior to 2.8.3 may throw a RangeError due to a stack overflow. The node resolution/composition phase uses recursive function calls without a depth bound. An attacker who can supply YAML for parsing can trigger a `RangeError: Maximum call stack size exceeded` with a small payload (~2–10 KB). The `RangeError` is not a `YAMLParseError`, so applications that only catch YAML-specific errors will encounter an unexpected exception type. Depending on the host application's exception handling, this can fail requests or terminate the Node.js process. Flow sequences allow deep nesting with minimal bytes (2 bytes per level: one `[` and one `]`). On the default Node.js stack, approximately 1,000–5,000 levels of nesting (2–10 KB input) exhaust the call stack. The exact threshold is environment-dependent (Node.js version, stack size, call stack depth at invocation). Note: the library's `Parser` (CST phase) uses a stack-based iterative approach and is not affected. Only the compose/resolve phase uses actual call-stack recursion. All three public parsing APIs are affected: `YAML.parse()`, `YAML.parseDocument()`, and `YAML.parseAllDocuments()`. Versions 1.10.3 and 2.8.3 contain a patch.

Timeline

1. Mar 26, 2026, 7:49 PM UTCCVE published
2. Mar 30, 2026, 11:26 AM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: no · Technical impact: partial

3. Mar 30, 2026, 11:26 AM UTCRecord last updated

Affected versions

• eemeli yaml

  From 2.0.0 · fixed in 2.8.3; From 1.0.0 · fixed in 1.10.3

• yamlnpm

  From 2.0.0 · fixed in 2.8.3

• yamlnpm

  From 1.0.0 · fixed in 1.10.3

References 5