Scriban up to 6.x sandbox

Summaryinfo

A vulnerability was found in Scriban up to 6.x. It has been rated as critical. Affected is an unknown function. The manipulation leads to sandbox. This vulnerability is documented as CVE-2026-74790. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Scriban up to 6.x and classified as critical. This issue affects an unknown function. The manipulation with an unknown input leads to a sandbox vulnerability. Using CWE to declare the problem leads to CWE-265. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-74790 since 08/16/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1611 for this issue.

Upgrading to version 7.0.0 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Scriban

Version

• 6.x

Website

• Product: https://github.com/scriban/scriban/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion