# CVE-2026-74784: Scriban before 7.2.0 Denial of Service via array.insert_at

> Attackers can crash the host process by supplying a large index to array.insert_at, causing an OutOfMemoryException in the Scriban template library.

- **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-24c8-4792-22hx, GHSA-wcrg-p6mv-jx2j

## What is CVE-2026-74784?

CVE-2026-74784 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 7.2.0 contains a denial of service vulnerability in the array.insert_at function that allocates unbounded null entries without respecting LoopLimit or LimitToString constraints. Attackers can supply a large index parameter to trigger OutOfMemoryException and crash the host process in under a second.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

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


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

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

Upgrade Scriban.Signed to 7.2.0 or later.

## Is CVE-2026-74784 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74784 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-74784 in the wild and no public exploit code.

Affected packages and fixed versions:
- Scriban.Signed (NuGet): affected all versions; fixed in 7.2.0
- Scriban.Signed (NuGet): affected all versions; fixed in 7.2.0
- scriban (NuGet): affected all versions; fixed in 7.2.0
- scriban (NuGet): affected all versions; fixed in 7.2.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-74784/ (Markdown: https://insights.sbomify.com/CVE-2026-74784/index.md)
```

## Sources

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

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