Skip to content
OpenAdvisories

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.

Affected products

VendorProductAffectedFixed
eemeli yaml >= 2.0.0, < 2.8.3, >= 1.0.0, < 1.10.3 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 14 node-yaml 2.8.3+~cs0.4.0-1 —
Debian 13 node-yaml No fix yet —
Debian 12 node-yaml No fix yet —
ReleasePackageFixed inAdvisory
Ubuntu 26.04 LTS node-yaml No fix yet —
Ubuntu 25.10 node-yaml No fix yet —
Ubuntu 24.04 LTS node-yaml No fix yet —
Ubuntu 22.04 LTS node-yaml No fix yet —
ReleasePackageFixed inAdvisory
SLES 15 SP7 alloy 1.17.1-150700.15.23.1 SUSE-SU-2026:2824-1
Show 2 more (older releases, extended support, other products)
ReleasePackageFixed inAdvisory
SLES for SAP 16.0 alloy 1.17.0-160000.1.1 SUSE-SU-2026:22575-1
SLES 16.0 alloy 1.17.0-160000.1.1 SUSE-SU-2026:22575-1
ReleasePackageFixed inAdvisory
openSUSE Tumbleweed alloy 1.17.0-1.1 openSUSE-SU-2026:11053-1
openSUSE Leap 16.0 alloy 1.17.0-160000.1.1 openSUSE-SU-2026:21251-1

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling argo-workflows-ui-4.0 4.0.3-r2 —
Wolfi rolling katib-earlystopping +8 0.19.0-r31 —
Wolfi rolling katib-suggestion-goptuna-compat 0.19.0-r40 —
Wolfi rolling langfuse-3-worker 3.164.0-r7 —
Wolfi rolling lerna 9.0.7-r2 —
Wolfi rolling nextcloud-server-33 33.0.6-r0 —
Wolfi rolling opensearch-dashboards-3-dashboards-reporting 3.5.0-r11 —
Wolfi rolling prism 5.14.3-r13 —
Wolfi rolling saf 1.6.0-r0 —
Wolfi rolling tileserver-gl 5.5.0-r11 —
Wolfi rolling vitess-23 23.0.3-r12 —

Public exploits

Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.

Third-party code, not reviewed by us. Public PoCs are sometimes fake or contain malware. Read the code first and run it only in an isolated lab, against systems you are authorised to test.

GitHub 1 repository

Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.

Affected packages

EcosystemPackageAffectedFixedRecord
npm yaml >= 2.0.0, < 2.8.3 2.8.3 GHSA-48c2-rrv3-qjmp
npm yaml >= 1.0.0, < 1.10.3 1.10.3 GHSA-48c2-rrv3-qjmp

Advisories 7

References