CVE-2026-33532: yaml is vulnerable to Stack Overflow via deeply nested YAML collections

Published Mar 25, 2026
·
Updated

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.

Other sources

Parsing a YAML document with yaml 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().

PoC

javascript const YAML = require('yaml');

// ~10 KB payload: 5000 levels of nested flow sequences const payload = '['.repeat(5000) + '1' + ']'.repeat(5000);

try { YAML.parse(payload); } catch (e) { console.log(e.constructor.name); // RangeError (NOT YAMLParseError) console.log(e.message); // Maximum call stack size exceeded }

Test environment: Node.js v24.12.0, macOS darwin arm64

| Version | Nesting Depth | Input Size | Result | |---|---|---|---| | 1.0.0 | 5,000 | 10,001 B | RangeError | | 1.10.2 | 5,000 | 10,001 B | RangeError | | 2.0.0 | 5,000 | 10,001 B | RangeError | | 2.8.2 | 5,000 | 10,001 B | RangeError | | 2.8.3 | 5,000 | 10,001 B | YAMLParseError |

Depth threshold on yaml 2.8.2:

| Nesting Depth | Input Size | Result | |---|---|---| | 500 | 1,001 B | Parses successfully | | 1,000 | 2,001 B | RangeError (threshold varies by stack size) | | 5,000 | 10,001 B | RangeError |

GitHub

Affected Software

5 affected componentsFixes available
npm/yaml>=1.0.0<1.10.3
1.10.3
npm/yaml>=2.0.0<2.8.3
2.8.3
Eemeli Yaml Node.js>=1.0.0<1.10.3
Eemeli Yaml Node.js>=2.0.0<2.8.3
IBM Concert Software<=1.0.0-2.3.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/yaml to a version that resolves this vulnerability.

    Fixed in 1.10.3
  2. Upgrade

    Upgrade npm/yaml to a version that resolves this vulnerability.

    Fixed in 2.8.3
  3. Upgrade

    Upgrade yaml to a version that resolves this vulnerability.

    Fixed in 1.10.3
  4. Upgrade

    Upgrade yaml to a version that resolves this vulnerability.

    Fixed in 2.8.3

Event History

Mar 25, 2026
Advisory Published
via GitHub·08:08 PM
Data Sourced
via GitHub·08:08 PM
DescriptionSeverityWeaknessAffected Software
Mar 26, 2026
CVE Published
via MITRE·07:49 PM
Data Sourced
via MITRE·07:49 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 27, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-33532?

CVE-2026-33532 has a medium severity rating due to the potential for a stack overflow error.

2

How do I fix CVE-2026-33532?

To fix CVE-2026-33532, upgrade the 'yaml' package to version 1.10.3 or 2.8.3.

3

Who is affected by CVE-2026-33532?

CVE-2026-33532 affects users of the 'yaml' package versions between 1.0.0 and 1.10.3, and 2.0.0 and 2.8.3.

4

What happens if I don't address CVE-2026-33532?

If CVE-2026-33532 is not addressed, attackers may exploit the vulnerability to induce a stack overflow, potentially leading to application crashes.

5

Is CVE-2026-33532 related to YAML file processing?

Yes, CVE-2026-33532 specifically involves a vulnerability during the parsing of YAML documents.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203