Skip to content
Applications

CVE-2026-74789

HIGH
High
EPSS 0.34%Patch availableAug 16, 2026

Template expressions can bypass LoopLimit causing CPU/memory exhaustion (DoS).

common questions

Is CVE-2026-74789 being exploited?

Not confirmed. CVE-2026-74789 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-74789?

CVE-2026-74789 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-74789?

Yes. A fix has been recorded for CVE-2026-74789. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-74789 affect?

CVE-2026-74789 affects Scriban <= 6.6.0, Applications rendering attacker-controlled Scriban templates, .NET apps embedding Scriban. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74789?

Upgrade Scriban to >=7.0.0; avoid rendering untrusted templates and add input/resource controls.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Scriban <= 6.6.0Applications rendering attacker-controlled Scriban templates.NET apps embedding Scriban
impact

Attacker-controlled templates can force high CPU or memory use, causing denial of service despite LoopLimit.

action required

Patch when possible

affected versions
scriban scriban
  • affected< 7.0.0
vendor says fixed in7.0.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free