How severe is CVE-2026-74791?

CVE-2026-74791 has a CVSS 3.x base score of 8.6, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-74791 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-74791?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-74791 published?

CVE-2026-74791 was published on 2026-08-16 and last updated on 2026-08-17.

CVE-2026-74791

CVE-2026-74791 is a high-severity vulnerability with a CVSS 3.x base score of 8.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-226.

Key facts

Severity: High (CVSS 3.x base score 8.6)
CVSS v4: 9.2
EPSS exploit prediction: 0% (19th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-226
Published: 2026-08-16
Last modified: 2026-08-17

Description

Scriban before 7.0.0 fails to clear the CachedTemplates dictionary when TemplateContext.Reset() is called, allowing cached templates to persist across reused contexts. Attackers can exploit request-dependent ITemplateLoader implementations to access previously authorized template content from earlier renders without triggering TemplateLoader.Load() again.

Frequently asked questions

What is CVE-2026-74791?: Scriban before 7.0.0 fails to clear the CachedTemplates dictionary when TemplateContext.Reset() is called, allowing cached templates to persist across reused contexts. Attackers can exploit request-dependent ITemplateLoader implementations to access previously authorized template content from earlier renders without triggering TemplateLoader.Load() again.
How severe is CVE-2026-74791?: CVE-2026-74791 has a CVSS 3.x base score of 8.6, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-74791 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-74791?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-74791 published?: CVE-2026-74791 was published on 2026-08-16 and last updated on 2026-08-17.

References

Other CWE-226 vulnerabilities

CVE-2026-13585 — High (CVSS 8.2): Allocation of Resources Without Limits and Throttling and Sensitive Information in Resource Not Removed Before Reuse in…
CVE-2025-0647 — High (CVSS 7.9): In certain Arm CPUs, a CPP RCTX instruction executed on one Processing Element (PE) may inhibit TLB invalidation when a…
CVE-2019-25560 — High (CVSS 7.5): Lyric Video Creator 2.1 contains a denial of service vulnerability that allows attackers to crash the application by…
CVE-2023-41138 — High (CVSS 7.5): The AppsAnywhere macOS client-privileged helper can be tricked into executing arbitrary commands with elevated…
CVE-2026-5795 — High (CVSS 7.4): In Eclipse Jetty, the class JASPIAuthenticator initiates the authentication checks, which set two ThreadLocal…
CVE-2026-32960 — Medium (CVSS 6.5): SD-330AC and AMC Manager provided by silex technology, Inc. contain an issue with a sensitive information in resource…

Browse all CWE-226 vulnerabilities →