Quick answers
- Is CVE-2026-124437 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-124437 being exploited in the wild.
- How severe is CVE-2026-124437?
- High severity, with a CVSS score of 7.5, published 8 November 2026.
- Which products and versions are affected?
- Scriban before 7.5.3; Scriban.Signed before 7.5.3.
- Is there a fix for CVE-2026-124437?
- Yes: fixed in 7.5.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-124437 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-124437?
- Check whether you run Scriban or Scriban.Signed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 7.5.3
Technical details
Multiple builtin functions (math.format, regex.replace, string.escape) and recursive operations bypass Scriban's resource limits (LimitToString, LoopLimit, CancellationToken), allowing untrusted template authors to trigger exponential memory allocation and CPU consumption. Attack vectors include huge format precision specifiers, exponential array comparison, uncapped BigInteger multiplication, and recursive function calls. The vulnerability requires no authentication or user interaction—submission of a small template under default TemplateContext is sufficient.
Affected products
- Scriban Scriban before 7.5.3
- Scriban Scriban.Signed before 7.5.3
Timeline
- 2026-10-24: disclosed
- 2026-11-08: advisory