Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-33532: yaml Uncontrolled Recursion Stack Overflow Denial of Service

Published Mar 26, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.3Medium · v3.1
EPSS0.50%43rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Eemeli
IdentifiersCVE-2026-33532CWE-674 · Uncontrolled Recursion

CVE-2026-33532 is an uncontrolled-recursion vulnerability in the JavaScript yaml parser and serialiser. In yaml versions before 1.10.3 on the 1.x branch and before 2.8.3 on the 2.x branch, the YAML node composition and resolution phase recursively processes nested structures without enforcing a depth bound. Deeply nested YAML flow sequences can exhaust the Node.js call stack and raise a RangeError. The affected public APIs are YAML.parse(), YAML.parseDocument(), and YAML.parseAllDocuments(). The iterative CST Parser phase is not affected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker able to supply deeply nested YAML can cause call-stack exhaustion with a relatively small payload. The resulting RangeError is not a YAMLParseError; applications that only handle YAML-specific parsing exceptions may fail requests or terminate the Node.js process. Successful exploitation can therefore cause denial of service. The exact nesting threshold depends on the Node.js version, configured stack size, and pre-existing call depth.

Mitigation

If you can’t patch tonight, do this now.

Do not parse untrusted YAML until a fixed version is deployed. Where untrusted YAML must be processed, impose application-level input-size and nesting-depth limits before calling the affected parsing APIs. Handle unexpected exceptions, including RangeError, in addition to YAML-specific parsing errors to reduce process-termination risk.

Remediation

Patch, then assume compromise.

Upgrade yaml to version 1.10.3 or later for the 1.x branch, or version 2.8.3 or later for the 2.x branch.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
EemeliYamlapplication
FAQ

Frequently asked questions

Is CVE-2026-33532 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-33532 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-33532?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-33532.
Is there a patch for CVE-2026-33532?
Upgrade yaml to version 1.10.3 or later for the 1.x branch, or version 2.8.3 or later for the 2.x branch.
What products are affected by CVE-2026-33532?
Eemeli Yaml.
How severe is CVE-2026-33532?
CVE-2026-33532 has a CVSS v3.1 score of 4.3 (Medium) and an EPSS score of 0.50% (43rd percentile) as of Sep 25, 2026.
Activity feed

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.