Skip to content
Applications

CVE-2026-74791

9.2
Critical
EPSS 0.27%Patch availableAug 16, 2026

Scriban cache persists across context resets, exposing previously authorized templates.

common questions

Is CVE-2026-74791 being exploited?

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

How severe is CVE-2026-74791?

CVE-2026-74791 is rated Critical with a CVSS score of 9.2. 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-74791?

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

What does CVE-2026-74791 affect?

CVE-2026-74791 affects Scriban < 7.0.0, Applications using Scriban TemplateContext/ITemplateLoader. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74791?

Upgrade Scriban to 7.0.0 or later immediately

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

executive summary
technical analysis
affected
Scriban < 7.0.0Applications using Scriban TemplateContext/ITemplateLoader
impact

Attackers can read previously rendered/authorized template content across reused TemplateContext by abusing request-dependent ITemplateLoader, leaking sensitive templates/data.

action required

Immediate action required

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