Service interruption via unbounded collection recursion
Published Mar 26, 2026 · Updated Mar 26, 2026
Uncontrolled recursion in yaml 1.0.0 through 1.10.2 and 2.0.0 through 2.8.2 allows remote authenticated users to interrupt services. The compose and resolve phase recursively descends nested flow collections without a depth bound, exhausting the JavaScript call stack on small crafted inputs. Reachability requires a host application to parse attacker-controlled YAML; the unexpected RangeError can fail a request or terminate the Node.js process.
Summary
What happened
Uncontrolled recursion in yaml 1.0.0 through 1.10.2 and 2.0.0 through 2.8.2 allows remote authenticated users to interrupt services. The compose and resolve phase recursively descends nested flow collections without a depth bound, exhausting the JavaScript call stack on small crafted inputs. Reachability requires a host application to parse attacker-controlled YAML; the unexpected RangeError can fail a request or terminate the Node.js process.
The record
- CVE
- CVE-2026-33532
- Published
- Mar 26, 2026
- Updated
- Mar 26, 2026
- Vendor
- Eemeli Aro
- Product
- yaml
- Classifications
- CWE-674, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 26, 2026CVE publishedPublication date reported by the CVE source.
- Mar 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.0.0, < 1.10.3
- Affected versionversion=>= 2.0.0, < 2.8.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-48c2-rrv3-qjmp proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo