← Back
GHSA-5rpf-x9jg-8j5p
Vulnerability in scriban (GHSA-5rpf-x9jg-8j5p)
Summary
vulnerability in scriban (GHSA-5rpf-x9jg-8j5p). Risk of unauthorized operations or information disclosure. Exploitable via ``TemplateContext.LimitToString``. Mitigation: upgrade to `6.6.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-5rpf-x9jg-8j5p** has been found in scriban.
Attackers can target a specific entry point like ``TemplateContext.LimitToString`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade scriban to **6.6.0** or later.
If unsure, ask your IT team or search "scriban GHSA-5rpf-x9jg-8j5p" on the vendor's site.
GHSA-5rpf-x9jg-8j5p (scriban) — CWE-770 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `TemplateContext.LimitToString` / `LoopLimit` / `LimitToString`
Patched: `6.6.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-770) exists in scriban. Attackers reach the vulnerable code path via ``TemplateContext.LimitToString`` without authentication.
📍 Affected scope
scriban — . Attack surface: `TemplateContext.LimitToString` / `LoopLimit` / `LimitToString`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6.6.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'scriban' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'scriban' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `scriban` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade scriban to 6.6.0ステージング環境で 6.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
nuget
scriban
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0"}]}]
nuget
Scriban.Signed
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0"}]}]