Scriban has an Infinite Recursion during Object Rendering Leads to Stack Overflow and Process Crash (Denial of Service)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

When 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…

Published by the source

19 Mar 2026, 21:31 UTC

Last modified by the source

6 Jul 2026, 13:06 UTC

Source last checked

26 Oct 2026, 17:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-grr9-747v-xvcp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-grr9-747v-xvcp

Advisory: Scriban has an Infinite Recursion during Object Rendering Leads to Stack Overflow and Process Crash (Denial of Service)
IDs: GHSA-grr9-747v-xvcp
Record: https://patchnext.com/advisories/ghsa-grr9-747v-xvcp (revision 1, source checked 26 Oct 2026, 17:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: scriban.signed 6.6.0; scriban 6.6.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet scriban.signed: affected <= 6.5.8; fixed in 6.6.0
- NuGet scriban: affected <= 6.5.8; fixed in 6.6.0

## Suggested inspection (read-only)
- NuGet scriban.signed: check the installed version with your package manager.
- NuGet scriban: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on scriban.signed, scriban.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-grr9-747v-xvcp (GitHub-reviewed advisory GHSA-grr9-747v-xvcp lists affected ranges: NuGet scriban >=0 =0 <=6.5.8)

Commands are suggestions: review each one before running it.