# CVE-2026-74790: Scriban before 7.0.0 MemberFilter Bypass via TemplateContext Cache

> Attackers can bypass sandbox restrictions in Scriban by reusing cached template contexts, exposing hidden properties and fields across requests.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-5wr9-m6jw-xx44, GHSA-6w6f-93jg-2qf5

## What is CVE-2026-74790?

CVE-2026-74790 is a critical vulnerability in scriban, published on 16 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2026-74790?

4 open source packages ship an affected version, including Scriban.Signed and scriban.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Scriban.Signed` | NuGet | All versions | 7.0.0 |
| `Scriban.Signed` | NuGet | All versions | 7.0.0 |
| `scriban` | NuGet | All versions | 7.0.0 |
| `scriban` | NuGet | All versions | 7.0.0 |

## How do I fix CVE-2026-74790?

Upgrade Scriban.Signed to 7.0.0 or later.

## Is CVE-2026-74790 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-74790 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74790 and fix it if it is affected.

What it is: CVE-2026-74790 is a critical vulnerability in scriban, published on 16 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-74790 exists.

Affected packages and fixed versions:
- Scriban.Signed (NuGet): affected all versions; fixed in 7.0.0
- Scriban.Signed (NuGet): affected all versions; fixed in 7.0.0
- scriban (NuGet): affected all versions; fixed in 7.0.0
- scriban (NuGet): affected all versions; fixed in 7.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74790/ (Markdown: https://insights.sbomify.com/CVE-2026-74790/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74790
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74790
- OSV: https://osv.dev/vulnerability/CVE-2026-74790

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74790/
Summaries are generated and may contain mistakes; the official description above is the record.