Security readout for executives and security teams
Plain-English summary
Applications using affected Scriban versions may accidentally show one user’s authorized template content to another user. The risk arises when applications reuse rendering contexts: resetting a context does not remove cached included templates, so earlier content can survive and bypass later authorization checks.
Executive priority
Treat as an urgent confidentiality issue where affected Scriban versions support shared or multi-tenant rendering. Prioritize internet-facing systems and services handling sensitive templates. Upgrade promptly, then verify context isolation. Lower priority only after confirming that the required context-reuse and request-dependent loader conditions do not exist.
Technical view
Before Scriban 7.0.0, TemplateContext.Reset() does not clear CachedTemplates. With reused contexts and request-dependent ITemplateLoader authorization, an included template loaded during an authorized render can be returned from cache during a later render without calling TemplateLoader.Load() again. This is a cross-request information disclosure and authorization-bypass condition consistent with CWE-226.
Likely exposure
Exposure requires Scriban before 7.0.0, TemplateContext reuse, template includes, and an ITemplateLoader whose authorization or content depends on the request. Internet-facing, multi-user, or multi-tenant services meeting these conditions deserve immediate review. Applications creating isolated contexts or not using request-dependent loaders may not be exploitable through this flaw.
Exploitation context
The supplied CVSS 4.0 score is 9.2, indicating remote, low-complexity, unauthenticated confidentiality impact. However, exploitation depends on application-specific context reuse and loader behavior. The CVE is not listed as KEV in the bundle, and the supplied sources provide no evidence of active exploitation.
Researcher notes
The central security boundary is the cache lookup bypassing a fresh TemplateLoader.Load() authorization decision. Assessment should focus on cache lifetime, TemplateContext pooling, include resolution, tenant separation, and whether authorization occurs exclusively inside the loader. Evidence supplied establishes the vulnerable mechanism and version boundary, but not real-world exploitation prevalence.
Mitigation direction
- Upgrade Scriban to version 7.0.0 or later.
- Review the vendor advisory for release-specific remediation guidance.
- Avoid reusing TemplateContext instances across users or authorization boundaries until upgraded.
- Ensure cached template content cannot cross tenant, user, or request boundaries.
Validation and detection
- Inventory applications and dependencies for Scriban versions before 7.0.0.
- Identify code paths that call TemplateContext.Reset() and subsequently reuse the context.
- Review ITemplateLoader implementations for request-, user-, tenant-, or permission-dependent decisions.
- Test that authorized template includes cannot persist into a later unauthorized render.
- Confirm CachedTemplates is cleared or isolated after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-226: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-74791 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.2 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N3.94VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.2CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
Base CVSS 3.1 score
8.6HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-x6m9-38vm-2xhf)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Scriban before 7.0.0 Authorization Bypass via Stale Include CacheCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Sensitive Information in Resource Not Removed Before Reuse
Sensitive Information in Resource Not Removed Before Reuse represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.