Scriban: array * int (ScriptArray .TryEvaluate) bypasses LoopLimit — incomplete fix for GHSA-c875-h985-hvrc, missed sibling of GHSA-24c8-4792-22hx

Exploitation

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

CVSS 4.0

5.5 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary The array multiplication operator (array integer) in Scriban allocates a result whose size is the product of the attacker-controlled integer and the array length, with no LoopLimit / LimitToString check and no overflow-safe arithmetic. A ~40-byte template forces a multi-gigabyte allocation, producing a denial-of-service. This is the unguarded sibling of operations that were hardened against the same class of abuse: string integer (gated by a LimitToString pre-check), array.insertat (gated by StepLoop/LoopLimit — the GHSA-24c8-4792-22hx fix shipped in 7.2.0, scored 8.7 High), and the range/iteration paths covered by GHSA-c875-h985-hvrc ("Built-in operations bypass LoopLimit", fixed 7.0.0). The same LoopLimit-based hardening pattern was applied to those operations but never to array integer. This can be observed directly in 7.0.0, the release where GHSA-c875 was patched: (1..5) 50000000 (and 1..N | array.size) correctly throws Exceeding number of iteration limit '1000', while…

Published by the source

26 Jun 2026, 21:01 UTC

Last modified by the source

6 Jul 2026, 13:03 UTC

Source last checked

26 Oct 2026, 17:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q6rr-fm2g-g5x8

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

# Patch Next advisory brief: GHSA-q6rr-fm2g-g5x8

Advisory: Scriban: array * int (ScriptArray .TryEvaluate) bypasses LoopLimit — incomplete fix for GHSA-c875-h985-hvrc, missed sibling of GHSA-24c8-4792-22hx
IDs: GHSA-q6rr-fm2g-g5x8
Record: https://patchnext.com/advisories/ghsa-q6rr-fm2g-g5x8 (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: Medium (CVSS 5.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 7.2.1; scriban 7.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet scriban.signed: affected >= 3.0.0, <= 7.2.0; fixed in 7.2.1
- NuGet scriban: affected >= 3.0.0, <= 7.2.0; fixed in 7.2.1

## 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-q6rr-fm2g-g5x8 (GitHub-reviewed advisory GHSA-q6rr-fm2g-g5x8 lists affected ranges: NuGet scriban >=3.0.0 =3.0.0 <=7.2.0)

Commands are suggestions: review each one before running it.