Is Scriban 7.1 vulnerable?
NuGet · 1 release from 7.1.0 to 7.1.0 · latest Scriban is 7.6.1 · checked 18 Nov 2026
Yes: 4 known advisories
Yes. Scriban 7.1.0, the last 7.1 release, is affected by 4 known security advisories (2 high, 2 medium), including CVE-2026-73061, CVE-2026-74784, CVE-2026-74783. Upgrade to 7.2.2 or later to fix all of them.
dotnet add package Scriban --version 7.2.2Is your project on an affected Scriban?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting Scriban 7.1.0
Scriban: Template Writes to Arbitrary CLR Properties via `TypedObjectAccessor` (Mass Assignment + `private` / `init` / `internal` Setter Bypass)
- Affected
- <7.2.2
- Fixed in
- 7.2.2
Scriban: ExpressionDepthLimit guard is non-enforcing — parser-recursion DoS in 6.6.0–7.2.0 (incomplete fix for GHSA-wgh7-7m3c-fx25 / GHSA-p6q4-fgr8-vx4p)
- Affected
- >=6.6.0 <7.2.1
- Fixed in
- 7.2.1
Scriban: array * int (ScriptArray<T>.TryEvaluate) bypasses LoopLimit — incomplete fix for GHSA-c875-h985-hvrc, missed sibling of GHSA-24c8-4792-22hx
- Affected
- >=3.0.0 <7.2.1
- Fixed in
- 7.2.1
Scriban: array.insert_at index parameter DoS bypasses LoopLimit and LimitToString
- Affected
- <7.2.0
- Fixed in
- 7.2.0
Which of your client projects are still on Scriban 7.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact Scriban version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other Scriban versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.