CVE-2026-33532: Yaml Yaml Is Vulnerable To Stack Vulnerability

MODERATE
Advisory Identifier: GHSA-48c2-rrv3-qjmp
CVSS 4.3
CWE-674
Published
Advisory Summary

CVE-2026-33532 is a MODERATE (CVSS 4.3) yaml is vulnerable to stack vulnerability (CWE-674: Uncontrolled Recursion) affecting Yaml libraries in the npm ecosystem. The issue involves yaml is vulnerable to stack overflow via deeply nested yaml collections. Remediation is available by upgrading affected packages to version 2.8.3, 1.10.3.

CVE-2026-33532 at a Glance

CVE Identifier CVE-2026-33532
GHSA Identifier GHSA-48c2-rrv3-qjmp
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification CWE-674: Uncontrolled Recursion
Affected Product Yaml
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 4.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability Low (A:L)

How to Fix CVE-2026-33532

To remediate this vulnerability, upgrade all affected Yaml dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

yaml fixed: 2.8.3
npm install yaml@2.8.3
yaml fixed: 1.10.3
npm install yaml@1.10.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls yaml

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-33532, inspect your project dependencies using npm:

npm ls yaml

Analyze the terminal output to locate any version of Yaml in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.8.3), your application is affected.

Note: The npm ls yaml command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-674: Uncontrolled Recursion, where the product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack. In Yaml, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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 |

CVE-2026-33532 Affected Yaml Versions

2 component(s)
Fixed Versions:
2.8.31.10.3
Product / Package Ecosystem Affected Versions Fixed Version
yaml
npm
≥ 2.0.0
< 2.8.3
2.8.3
yaml
npm
≥ 1.0.0
< 1.10.3
1.10.3

References

Frequently Asked Questions

What is CVE-2026-33532?
CVE-2026-33532 is a security vulnerability in Yaml involving yaml is vulnerable to Stack Overflow via deeply nested YAML collections under CWE-674: Uncontrolled Recursion.
Which Yaml versions are affected?
Affected versions include releases prior to 2.8.3, 1.10.3 across affected packages: yaml.
What version fixes CVE-2026-33532?
Upgrading to 2.8.3, 1.10.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is yaml affected?
Yes, yaml is affected in releases prior to 2.8.3, 1.10.3. Upgrade your dependency to 2.8.3, 1.10.3 or later.
What is the CVSS score of CVE-2026-33532?
CVE-2026-33532 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L.
What CWE is associated with CVE-2026-33532?
CVE-2026-33532 is classified under CWE-674: Uncontrolled Recursion (The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.).
How can I check npm dependencies for CVE-2026-33532?
Run the dependency tree command: 'npm ls yaml'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-48c2-rrv3-qjmp",
  "modified" : "2026-03-27T21:34:51Z",
  "published" : "2026-03-25T20:08:24Z",
  "aliases" : [ "CVE-2026-33532" ],
  "summary" : "yaml is vulnerable to Stack Overflow via deeply nested YAML collections",
  "details" : "Parsing a YAML document with `yaml` may throw a RangeError due to a stack overflow.\n\nThe 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.\n\nFlow 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).\n\nNote: 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.\n\nAll three public parsing APIs are affected: `YAML.parse()`, `YAML.parseDocument()`, and `YAML.parseAllDocuments()`.\n\n### PoC\n\n```javascript\nconst YAML = require('yaml');\n\n// ~10 KB payload: 5000 levels of nested flow sequences\nconst payload = '['.repeat(5000) + '1' + ']'.repeat(5000);\n\ntry {\n  YAML.parse(payload);\n} catch (e) {\n  console.log(e.constructor.name); // RangeError (NOT YAMLParseError)\n  console.log(e.message);          // Maximum call stack size exceeded\n}\n```\n\nTest environment: Node.js v24.12.0, macOS darwin arm64\n\n| Version | Nesting Depth | Input Size | Result |\n|---|---|---|---|\n| 1.0.0 | 5,000 | 10,001 B | RangeError |\n| 1.10.2 | 5,000 | 10,001 B | RangeError |\n| 2.0.0 | 5,000 | 10,001 B | RangeError |\n| 2.8.2 | 5,000 | 10,001 B | RangeError |\n| 2.8.3 | 5,000 | 10,001 B | YAMLParseError |\n\nDepth threshold on yaml 2.8.2:\n\n| Nesting Depth | Input Size | Result |\n|---|---|---|\n| 500 | 1,001 B | Parses successfully |\n| 1,000 | 2,001 B | RangeError (threshold varies by stack size) |\n| 5,000 | 10,001 B | RangeError |",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "yaml"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.8.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "yaml"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.0.0"
      }, {
        "fixed" : "1.10.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/eemeli/yaml/security/advisories/GHSA-48c2-rrv3-qjmp"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33532"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/eemeli/yaml/commit/1e84ebbea7ec35011a4c61bbb820a529ee4f359b"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/eemeli/yaml"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/eemeli/yaml/releases/tag/v1.10.3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/eemeli/yaml/releases/tag/v2.8.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-674" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-25T20:08:24Z",
    "nvd_published_at" : "2026-03-26T20:16:15Z"
  }
}