PatchSiren cyber security CVE debrief
CVE-2026-73061 scriban CVE debrief
The Scriban library before version 7.2.2 is vulnerable to an access-modifier bypass issue in the TypedObjectAccessor component. This vulnerability allows template code to write to CLR object properties without adhering to setter-visibility checks. Consequently, attackers can modify properties with private, internal, or init-only setters and perform mass assignment on public-setter properties. This can lead to the permanent alteration of live host objects after template rendering. Affected product deployments should be reviewed for exposure, and owners should prioritize upgrading to a patched version to prevent potential attacks.
- Vendor
- scriban
- Product
- Unknown
- CVSS
- CRITICAL 9.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-16
- Original CVE updated
- 2026-08-31
- Advisory published
- 2026-08-16
- Advisory updated
- 2026-08-31
Who should care
Developers and administrators using Scriban for template rendering should be aware of this vulnerability and take necessary actions to upgrade to a patched version or implement mitigating controls. Affected operators, platforms, and security teams should review the vulnerability and its potential impact on their environments. Vulnerability management and security teams should prioritize remediation efforts and monitor for potential attacks.
Technical summary
The Scriban library before version 7.2.2 is vulnerable to an access-modifier bypass issue in the TypedObjectAccessor component. This vulnerability allows template code to write to CLR object properties without adhering to setter-visibility checks. Consequently, attackers can modify properties with private, internal, or init-only setters and perform mass assignment on public-setter properties. This can lead to the permanent alteration of live host objects after template rendering. The vulnerability affects Scriban versions prior to 7.2.2 and can be mitigated by upgrading to a patched version.
Defensive priority
Organizations using Scriban before version 7.2.2 should prioritize upgrading to a patched version to prevent potential attacks.
Recommended defensive actions
- Upgrade to Scriban version 7.2.2 or later
- Review and restrict template code execution privileges
- Implement compensating controls to monitor and limit CLR object property modifications
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The CVE-2026-73061 record indicates that Scriban before 7.2.2 contains an access-modifier bypass vulnerability in TypedObjectAccessor. This allows template code to write CLR object properties without setter-visibility checks. However, detailed information about affected configurations and vendor remediation is limited in the provided source corpus.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-73061 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-73061
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-73061 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-73061
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/scriban/scriban/security/advisories/GHSA-7jvp-hj45-2f2m
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/scriban-before-arbitrary-property-write-via-typedobjectaccessor
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.