Scriban is vulnerable to Uncontrolled Resource Consumption
87
CVE Score
High
Uncontrolled Resource Consumption
Untrusted template authors could exhaust memory or CPU because string builtins skipped allocation guards and array comparison, BigInteger multiplication, and function recursion escaped runtime limits. The risk mattered when an application rendered their templates with the default TemplateContext; the advisory said a short template required nothing exposed by the host. The fix adds guards and bounds for those operations.
Upgrade the Scriban package to 7.5.3 or later.
You are affected if you are using a version that falls within the vulnerable range of Scriban.
0.1.0 - 7.5.2
Fixed in 7.5.3Scriban is vulnerable to Uncontrolled Resource Consumption in versions 0.1.0 - 7.5.2.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.