CVE-2026-74794
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 0.49 % · percentile 42.77 % · 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 6.6.0 contains an infinite recursion vulnerability in object rendering when the ObjectRecursionLimit property defaults to unlimited. Attackers can supply circular reference objects to the template context, exhausting stack space and triggering an uncatchable StackOverflowException that terminates the hosting process.
Read the publisher's advisoryScriban before 6.6.0 contains an infinite recursion vulnerability in object rendering when the ObjectRecursionLimit property defaults to unlimited. Attackers can supply circular reference objects to the template context, exhausting stack space and triggering an uncatchable StackOverflowException that terminates the hosting process.
Read the publisher's advisoryScriban before 6.6.0 contains an infinite recursion vulnerability in object rendering when the ObjectRecursionLimit property defaults to unlimited. Attackers can supply circular reference objects to the template context, exhausting stack space and triggering an uncatchable StackOverflowException that terminates the hosting process.
Read the publisher's advisoryWhen Scriban renders an object that contains a circular reference, it traverses the object's members infinitely. Because the `ObjectRecursionLimit` property defaults to unlimited, this behavior exhausts the thread's stack space, triggering an uncatchable `StackOverflowException` that immediately terminates the hosting process. When rendering objects (e.g., `{{ obj }}`), the Scriban rendering engine recursively inspects and formats the object's properties. To prevent infinite loops caused by deeply nested or circular data structures, `TemplateContext` contains an `ObjectRecursionLimit` property. However, this property currently defaults to `0` (unlimited). If the data context pushed into the template contains a circular reference, the renderer will recurse indefinitely. This is especially dangerous for web applications that map user-controlled payloads (like JSON) directly to rendering contexts, or for applications that pass ORM objects (like Entity Framework models, which frequently contain circular navigation properties) into the template. #### Proof of Concept (PoC) The following C# code demonstrates the vulnerability. Executing this will cause an immediate, fatal `StackOverflowException`, bypassing any standard error handling. ```csharp using Scriban; using Scriban.Runtime; var template = Template.Parse("{{ a }}"); var context = new TemplateContext(); var a = new ScriptObject(); // Introduce a cycle a["self"] = a; context.PushGlobal(new ScriptObject { { "a", a } }); try { // This crashes the entire process immediately template.Render(context); } catch (Exception ex) { // This will never execute because StackOverflowException Console.WriteLine("Caught exception: " + ex.Message); } ``` #### Impact This vulnerability allows a Denial of Service (DoS) attack. If a malicious user can manipulate the data structure passed to the renderer to include a cyclic reference, or if the application passes a complex object graph to an untrusted template, the entire .NET hosting process will crash. #### Suggested Remediation Update `TemplateContext.cs` to set `ObjectRecursionLimit` to a safe default, such as `20`. ```csharp public int ObjectRecursionLimit { get; set; } = 20; ``` By implementing this default, circular references will gracefully result in a catchable `ScriptRuntimeException` rather than a fatal process crash.
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.49 % · percentile 42.77 % · 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-74794 · 19 Nov 2026 16:46:59 UTC
CVE-2026-74794 · 18 Nov 2026 15:46:44 UTC
CVE-2026-74794 · 17 Nov 2026 15:26:11 UTC
CVE-2026-74794 · 17 Nov 2026 02:39:16 UTC
CVE-2026-74794 · 15 Nov 2026 14:45:34 UTC
CVE-2026-74794 · 14 Nov 2026 16:37:01 UTC
CVE-2026-74794 · 13 Nov 2026 19:59:34 UTC
CVE-2026-74794 · 12 Nov 2026 18:18:51 UTC
CVE-2026-74794 · 10 Nov 2026 20:24:10 UTC
CVE-2026-74794 · 09 Nov 2026 21:04:24 UTC
CVE-2026-74794 · 08 Nov 2026 15:12:21 UTC
CVE-2026-74794 · 07 Nov 2026 16:07:52 UTC
CVE-2026-74794 · 06 Nov 2026 19:10:17 UTC
CVE-2026-74794 · 05 Nov 2026 22:49:22 UTC
CVE-2026-74794 · 05 Nov 2026 02:54:06 UTC
CVE-2026-74794 · 03 Nov 2026 16:59:18 UTC
CVE-2026-74794 · 02 Nov 2026 23:59:04 UTC
CVE-2026-74794 · 01 Nov 2026 23:58:58 UTC
CVE-2026-74794 · 01 Nov 2026 03:04:52 UTC
CVE-2026-74794 · 31 Oct 2026 01:52:30 UTC
CVE-2026-74794 · 29 Oct 2026 18:29:26 UTC
CVE-2026-74794 · 28 Oct 2026 19:55:37 UTC
CVE-2026-74794 · 27 Oct 2026 15:46:19 UTC
CVE-2026-74794 · 27 Oct 2026 00:23:05 UTC
CVE-2026-74794 · 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-59959 · Published
euvd · EUVD-2026-59959 · Published
euvd · EUVD-2026-59959 · Published
euvd · EUVD-2026-59959 · Published
euvd · EUVD-2026-59959 · Published
euvd · EUVD-2026-59959 · Published
euvd · EUVD-2026-59959 · Published
euvd · EUVD-2026-59959 · Published
euvd · EUVD-2026-59959 · Published
euvd · EUVD-2026-59959 · Published
euvd · EUVD-2026-59959 · Published
nvd · CVE-2026-74794 · Published
osv · GHSA-grr9-747v-xvcp · Published
cve-program · CVE-2026-74794 · Published