chore(deps): 🔗 update dependency yaml to v1.10.3 [security] - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
yaml (source)	1.10.0 → 1.10.3

GitHub Vulnerability Alerts

CVE-2026-33532

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

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

---

Release Notes

eemeli/yaml (yaml)

v1.10.3

Compare Source

v1.10.2

Compare Source

• Allow for unindented comment after node props (prettier/prettier#10510)

v1.10.1

Compare Source

This release backports the following non-breaking fixes made during the work on yaml@2 on top of yaml@1.10.0:

• Support for __proto__ as mapping key & anchor identifier (#​192)
• Fix broken TS type for BigInt toggle
• Dump long keys properly (#​195)
• When folding highly indented lines, require at least minContentWidth chars on the first line (#​196)
• Fix YAML.stringify() for certain null values (#​197)
• Do not break escaped chars with escaped newlines (#​237, awslabs/cdk8s#494)
• Set type: "module" within browser/dist/ (#​208)
• Use CommonJS for the browser endpoints yaml/types & yaml/util (#​208)
• Always stringify non-Node object keys using explicit notation (#​218)
• Specify node type of Document.Parsed.contents (#​221)
• Add missing type for CST Node.rangeAsLinePos (#​222)
• Prefer literal over folded block scalar when lineWidth=0 is set (#​232)
• Allow for empty lines after node props (#​242)
• Update dev dependencies

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 00cf2ee

Command	Status	Duration	Result
nx affected --target=test	✅ Succeeded	2m 21s	View ↗
nx affected --target=build	✅ Succeeded	58s	View ↗
nx affected --target=lint	✅ Succeeded	15s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-03-27 02:54:24 UTC