CVE-2026-74790
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 0.47 % · percentile 41.49 % · scored 19 Nov 2026.
Saved 19 Nov 2026 16:46:59 UTC · View this risk record (JSON)
No access to your tenant or devices. Every item links to its source. What this means
Scriban before 7.0.0 caches TypedObjectAccessor by Type only without considering MemberFilter changes, allowing reused TemplateContext instances to expose members that should be hidden. Attackers can access filtered properties and fields by reusing a TemplateContext after tightening its MemberFilter, bypassing sandbox policies across requests or tenants.
Read the publisher's advisoryScriban before 7.0.0 caches TypedObjectAccessor by Type only without considering MemberFilter changes, allowing reused TemplateContext instances to expose members that should be hidden. Attackers can access filtered properties and fields by reusing a TemplateContext after tightening its MemberFilter, bypassing sandbox policies across requests or tenants.
Read the publisher's advisoryScriban before 7.0.0 caches TypedObjectAccessor by Type only without considering MemberFilter changes, allowing reused TemplateContext instances to expose members that should be hidden. Attackers can access filtered properties and fields by reusing a TemplateContext after tightening its MemberFilter, bypassing sandbox policies across requests or tenants.
Read the publisher's advisory## Summary `TemplateContext` caches type accessors by `Type` only, but those accessors are built using the current `MemberFilter` and `MemberRenamer`. When a `TemplateContext` is reused and the filter is tightened for a later render, Scriban still reuses the old accessor and continues exposing members that should now be hidden. ## Details The relevant code path is: - `TemplateContext.GetMemberAccessor()` caches accessors in `_memberAccessors` by `Type` in `src/Scriban/TemplateContext.cs` lines 850–863. - For plain .NET objects, `GetMemberAccessorImpl()` creates a new `TypedObjectAccessor(type, _keyComparer, MemberFilter, MemberRenamer)` in `src/Scriban/TemplateContext.cs` lines 909–939. - `TypedObjectAccessor` stores the current filter and precomputes the exposed member set in its constructor and `PrepareMembers()` in `src/Scriban/Runtime/Accessors/TypedObjectAccessor.cs` lines 33–40 and 119–179. - Member access later goes through `ScriptMemberExpression.GetValue()` in `src/Scriban/Syntax/Expressions/ScriptMemberExpression.cs` lines 67–95, which uses the cached accessor. - `TemplateContext.Reset()` does **not** clear `_memberAccessors` in `src/Scriban/TemplateContext.cs` lines 877–902. As a result, once a permissive accessor has been created for a given type, changing `TemplateContext.MemberFilter` later does not take effect for that type on the same reused context. This is especially relevant because the Scriban docs explicitly recommend `TemplateContext.MemberFilter` for indirect .NET object exposure. --- ## Proof of Concept ### Setup ```bash mkdir scriban-poc2 cd scriban-poc2 dotnet new console --framework net8.0 dotnet add package Scriban --version 6.6.0 ``` ### `Program.cs` ```csharp using System.Reflection; using Scriban; using Scriban.Runtime; var template = Template.Parse("{{ model.secret }}"); var context = new TemplateContext { EnableRelaxedMemberAccess = false }; var globals = new ScriptObject(); globals["model"] = new SensitiveModel(); context.PushGlobal(globals); context.MemberFilter = _ => true; Console.WriteLine("first=" + template.Render(context)); context.Reset(); var globals2 = new ScriptObject(); globals2["model"] = new SensitiveModel(); context.PushGlobal(globals2); context.MemberFilter = member => member.Name == nameof(SensitiveModel.Public); Console.WriteLine("second=" + template.Render(context)); sealed class SensitiveModel { public string Public => "ok"; public string Secret => "leaked"; } ``` ### Run ```bash dotnet run ``` ### Actual Output ``` first=leaked second=leaked ``` ### Expected Behavior The second render should fail or stop exposing `Secret`, because the filter only allows `Public` and `EnableRelaxedMemberAccess` is disabled. This reproduces a direct filter bypass caused by the stale cached accessor. --- ## Impact This is a protection-mechanism bypass. Applications that use `TemplateContext.MemberFilter` as part of their sandbox or object-exposure policy can unintentionally expose hidden members across requests when they reuse a `TemplateContext`. The impact includes: - Unauthorized read access to filtered properties or fields - Unauthorized writes if the filtered member also has a setter - Policy bypass across requests, users, or tenants when contexts are pooled
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 0.47 % · percentile 41.49 % · scored 19 Nov 2026.
Saved 19 Nov 2026 16:46:59 UTC · View this risk record (JSON)
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
CVE-2026-74790 · 19 Nov 2026 16:46:59 UTC
CVE-2026-74790 · 18 Nov 2026 15:46:44 UTC
CVE-2026-74790 · 17 Nov 2026 15:26:11 UTC
CVE-2026-74790 · 17 Nov 2026 02:39:16 UTC
CVE-2026-74790 · 15 Nov 2026 14:45:34 UTC
CVE-2026-74790 · 14 Nov 2026 16:37:01 UTC
CVE-2026-74790 · 13 Nov 2026 19:59:34 UTC
CVE-2026-74790 · 12 Nov 2026 18:18:51 UTC
CVE-2026-74790 · 10 Nov 2026 20:24:10 UTC
CVE-2026-74790 · 09 Nov 2026 21:04:24 UTC
CVE-2026-74790 · 08 Nov 2026 15:12:21 UTC
CVE-2026-74790 · 07 Nov 2026 16:07:52 UTC
CVE-2026-74790 · 06 Nov 2026 19:10:17 UTC
CVE-2026-74790 · 05 Nov 2026 22:49:22 UTC
CVE-2026-74790 · 05 Nov 2026 02:54:06 UTC
CVE-2026-74790 · 03 Nov 2026 16:59:18 UTC
CVE-2026-74790 · 02 Nov 2026 23:59:04 UTC
CVE-2026-74790 · 01 Nov 2026 23:58:58 UTC
CVE-2026-74790 · 01 Nov 2026 03:04:52 UTC
CVE-2026-74790 · 31 Oct 2026 01:52:30 UTC
CVE-2026-74790 · 29 Oct 2026 18:29:26 UTC
CVE-2026-74790 · 28 Oct 2026 19:55:37 UTC
CVE-2026-74790 · 27 Oct 2026 15:46:19 UTC
CVE-2026-74790 · 27 Oct 2026 00:23:05 UTC
CVE-2026-74790 · 25 Oct 2026 15:18:41 UTC
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2026-59956 · Published
euvd · EUVD-2026-59956 · Published
euvd · EUVD-2026-59956 · Published
euvd · EUVD-2026-59956 · Published
euvd · EUVD-2026-59956 · Published
euvd · EUVD-2026-59956 · Published
euvd · EUVD-2026-59956 · Published
euvd · EUVD-2026-59956 · Published
euvd · EUVD-2026-59956 · Published
euvd · EUVD-2026-59956 · Published
euvd · EUVD-2026-59956 · Published
euvd · EUVD-2026-59956 · Published
nvd · CVE-2026-74790 · Published
osv · GHSA-5wr9-m6jw-xx44 · Published
cve-program · CVE-2026-74790 · Published