# CVE-2026-74795: Scriban before 6.6.0 Denial of Service via Uncontrolled Recursion

> Attackers can cause denial of service by submitting deeply nested templates to the Scriban library, crashing the hosting application via stack exhaustion.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-wgh7-7m3c-fx25, GHSA-x4hp-vj3w-6w2m

## What is CVE-2026-74795?

CVE-2026-74795 is a high-severity denial of service vulnerability in scriban, published on 16 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Scriban before 6.6.0 contains an uncontrolled recursion vulnerability in its recursive-descent parser. The parser does not enforce a default expression depth limit (the ExpressionDepthLimit property in ParserOptions defaults to null/disabled), so an attacker who controls template input can supply a deeply nested template (e.g., thousands of nested parentheses or blocks) that exhausts thread stack space and raises a StackOverflowException. Because a StackOverflowException cannot be caught in .NET, this causes immediate, unrecoverable termination of the hosting process, resulting in a denial of service. Applications that process untrusted or user-supplied templates can be exploited remotely without authentication.

Weakness: CWE-674 (Uncontrolled Recursion)

## Which versions are affected by CVE-2026-74795?

4 open source packages ship an affected version, including Scriban.Signed and scriban.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Scriban.Signed` | NuGet | All versions | 6.6.0 |
| `Scriban.Signed` | NuGet | All versions | 6.6.0 |
| `scriban` | NuGet | All versions | 6.6.0 |
| `scriban` | NuGet | All versions | 6.6.0 |

## How do I fix CVE-2026-74795?

Upgrade Scriban.Signed to 6.6.0 or later.

## Is CVE-2026-74795 being exploited?

There is no known exploitation of CVE-2026-74795 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74795 and fix it if it is affected.

What it is: CVE-2026-74795 is a high-severity denial of service vulnerability in scriban, published on 16 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74795 in the wild and no public exploit code.

Affected packages and fixed versions:
- Scriban.Signed (NuGet): affected all versions; fixed in 6.6.0
- Scriban.Signed (NuGet): affected all versions; fixed in 6.6.0
- scriban (NuGet): affected all versions; fixed in 6.6.0
- scriban (NuGet): affected all versions; fixed in 6.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74795/ (Markdown: https://insights.sbomify.com/CVE-2026-74795/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74795
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74795
- OSV: https://osv.dev/vulnerability/CVE-2026-74795

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74795/
Summaries are generated and may contain mistakes; the official description above is the record.