CVE-2026-74790
Scriban cache bug exposes filtered object members when TemplateContext is reused.
Is CVE-2026-74790 being exploited?
Not confirmed. CVE-2026-74790 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.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-74790?
CVE-2026-74790 is rated Critical. 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-74790?
Yes. A fix has been recorded for CVE-2026-74790. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74790 affect?
CVE-2026-74790 affects Scriban < 7.0.0, Applications using Scriban templates. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74790?
Upgrade to Scriban 7.0.0+, restart affected services, avoid sharing TemplateContext instances.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Reused TemplateContext can bypass MemberFilter/sandboxing, allowing attackers to read previously filtered properties/fields and expose sensitive data.
Immediate action required
- affected< 7.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.