Process crash via non-enforcing parser depth limit
Published Aug 16, 2026 · Updated Aug 16, 2026
Denial of service in Scriban 6.6.0 through 7.2.0 allows attackers to crash the host process via deeply nested template expressions. In src/Scriban/Parsing/Parser.Expressions.cs, EnterExpression increments depth and logs an error when ExpressionDepthLimit is exceeded, but it neither aborts parsing nor unwinds recursion, so ParseExpression continues through nested parentheses, arrays, objects, and unary operators until .NET raises an uncatchable StackOverflowException. Exposure requires attacker influence over template text passed to Template.Parse or Template.ParseLiquid, or over strings re-parsed by object.eval or object.eval_template; the consequence is bounded to availability because the process terminates immediately.
Summary
What happened
Denial of service in Scriban 6.6.0 through 7.2.0 allows attackers to crash the host process via deeply nested template expressions. In src/Scriban/Parsing/Parser.Expressions.cs, EnterExpression increments depth and logs an error when ExpressionDepthLimit is exceeded, but it neither aborts parsing nor unwinds recursion, so ParseExpression continues through nested parentheses, arrays, objects, and unary operators until .NET raises an uncatchable StackOverflowException. Exposure requires attacker influence over template text passed to Template.Parse or Template.ParseLiquid, or over strings re-parsed by object.eval or object.eval_template; the consequence is bounded to availability because the process terminates immediately.
The record
- CVE
- CVE-2026-74783
- Published
- Aug 16, 2026
- Updated
- Aug 16, 2026
- Vendor
- Scriban
- Product
- Scriban
- Classifications
- CWE-674, CAPEC-230, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 16, 2026CVE publishedPublication date reported by the CVE source.
- Aug 16, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
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-6q7j-xr26-3h2c console-project 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