Skip to content
Applications

CVE-2026-74795

HIGH
High
EPSS 0.32%Patch availableAug 16, 2026

Uncontrolled recursion in Scriban parser allows remote templates to crash host process.

common questions

Is CVE-2026-74795 being exploited?

Not confirmed. CVE-2026-74795 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.32% probability of exploitation in the next 30 days.

How severe is CVE-2026-74795?

CVE-2026-74795 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-74795?

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

What does CVE-2026-74795 affect?

CVE-2026-74795 affects Scriban < 6.6.0, Applications using Scriban to process untrusted templates, .NET services hosting Scriban. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74795?

Upgrade to Scriban >=6.6.0; validate or limit template recursion depth (ExpressionDepthLimit).

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 using Scriban to process untrusted templates.NET services hosting Scriban
impact

Remote unauthenticated DoS: attacker-supplied deeply nested templates trigger StackOverflowException and terminate the .NET host process.

action required

Immediate action required

affected versions
scriban scriban
  • affected< 6.6.0
vendor says fixed in6.6.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