Scriban vulnerabilities
Scriban is a fast, powerful, safe and lightweight scripting language and engine for .NET, which was primarily developed for text templating with a compatibility mode for parsing liquid templates.
- Registry
- NuGet
- Latest
- 7.6.1
- License
- BSD-2-Clause
15 known advisories
The latest version, 7.6.1, is not affected by any of them. Projects on older versions may be.
dotnet add package Scriban --version 7.6.1Is 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
Security advisories for Scriban
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
Scriban has Multiple Denial-of-Service Vectors via Unbounded Resource Consumption During Expression Evaluation
- Affected
- <7.0.0
- Fixed in
- 7.0.0
Scriban: Denial of Service via Unbounded Cumulative Template Output Bypassing LimitToString
- Affected
- <7.0.0
- Fixed in
- 7.0.0
Scriban has Uncontrolled Recursion in `object.to_json` Causing Unrecoverable Process Crash via StackOverflowException
- Affected
- <7.0.0
- Fixed in
- 7.0.0
Scriban: Uncontrolled Memory Allocation via string.pad_left/pad_right Allows Remote Denial of Service
- Affected
- <7.0.0
- Fixed in
- 7.0.0
Scriban: Built-in operations bypass LoopLimit and delay cancellation, enabling Denial of Service
- Affected
- <7.0.0
- Fixed in
- 7.0.0
Scriban: Sandbox escape due to TypedObjectAccessorcache bypassing MemberFilter after TemplateContext reuse
- Affected
- <7.0.0
- Fixed in
- 7.0.0
Scriban has an authorization bypass due to stale include cache surviving TemplateContext.Reset()
- Affected
- <7.0.0
- Fixed in
- 7.0.0
Scriban has a Stack Overflow via Nested Array Initializers That Bypass the ExpressionDepthLimit Fix
- Affected
- <7.0.0
- Fixed in
- 7.0.0
Scriban Affected by Memory Exhaustion (OOM) via Unbounded String Generation (Denial of Service)
- Affected
- <6.6.0
- Fixed in
- 6.6.0
Scriban has an Infinite Recursion during Object Rendering Leads to Stack Overflow and Process Crash (Denial of Service)
- Affected
- <6.6.0
- Fixed in
- 6.6.0
Scriban has Uncontrolled Recursion in Parser Leads to Stack Overflow and Process Crash (Denial of Service)
- Affected
- <6.6.0
- Fixed in
- 6.6.0
Is your Scriban version vulnerable?
- Scriban 7.6No known advisories in 7.6.1
- Scriban 7.5No known advisories in 7.5.3
- Scriban 7.4No known advisories in 7.4.0
- Scriban 7.3No known advisories in 7.3.0
- Scriban 7.2No known advisories in 7.2.7
- Scriban 7.14 advisories in 7.1.0
- Scriban 6.612 advisories in 6.6.0
- Scriban 6.514 advisories in 6.5.8
- Scriban 6.414 advisories in 6.4.0
- Scriban 6.314 advisories in 6.3.0
- Scriban 6.214 advisories in 6.2.1
- Scriban 6.114 advisories in 6.1.0
- Scriban 5.1214 advisories in 5.12.1
- Scriban 5.1114 advisories in 5.11.0
- Scriban 5.1014 advisories in 5.10.0
- Scriban 5.914 advisories in 5.9.1
- Scriban 5.814 advisories in 5.8.0
- Scriban 5.714 advisories in 5.7.0
Which of your client projects still run an old Scriban?
NPMscan reads the packages.lock.json and .csproj files in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other NuGet packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the NuGet registry.