node-yaml: `yaml` is a YAML parser and serialiser for JavaScript
CVE-2026-33532 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-33532, released March 26, 2026. It is not reported as exploited. Patch Radar priority: Routine.
`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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| alloy · opensuse-leap 16.0 | 1.17.0-160000.1.1 | OPENSUSE-SU-2026:21251-1 | Jul 7, 2026 |
| alloy · sles 15.7 | 1.17.1-150700.15.23.1 | SUSE-SU-2026:2824-1 | Jul 9, 2026 |
| alloy · sles 16.0 | 1.17.0-160000.1.1 | SUSE-SU-2026:22575-1 | Jul 7, 2026 |
| node-yaml · Debian 14 | 2.8.3+~cs0.4.0-1 | DEBIAN-CVE-2026-33532 | Mar 26, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.