CVE-2026-100668
Deferred Deferred - Pending Action

Twig Sandbox Escape in Grav CMS

Publication date: 2026-09-26

Last updated on: 2026-09-26

Assigner: VulnCheck

Description
Grav 2.0.0 through 2.0.24 contain a Twig content sandbox escape. The `array` filter (and its identical function form) is on the sandbox allowlist but is registered without the needs_is_sandboxed guard that print_r, vardump, json_encode, yaml_encode and string carry, and its implementation calls toArray() — or falls back to an (array) cast — without consulting the sandbox method allowlist. Because the `grav` Twig global is the raw Pimple-based dependency injection container, a user who can author Twig in page content can evaluate `grav|array` to read the container's private $values array, including the un-redacted Config service; a second array cast returns the entire configuration tree, disclosing plugin credentials, SMTP and OAuth secrets, Redis passwords, proxy URLs and the security.* subtree that the sandbox's redaction is meant to hide. Because the payload is stored in page content, the disclosed configuration is rendered to anonymous visitors. Grav 1.7 is not affected as it has no Twig content sandbox. Fixed in Grav 2.0.25.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-26
Last Modified
2026-09-26
Generated
2026-09-26
AI Q&A
2026-09-26
EPSS Evaluated
N/A
NVD
CVE-2026-100668
EUVD
EUVD-2026-87762

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
grav grav From 2.0.0 (inc) to 2.0.24 (inc)
grav grav 2.0.25

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a sandbox escape in Grav CMS versions 2.0.0 through 2.0.24 that allows attackers with limited privileges to bypass Twig content sandbox restrictions. The issue involves the unguarded `array` filter in Twig, which can cast the dependency-injection container to an array, exposing sensitive configuration data such as plugin credentials, API keys, Redis passwords, and security settings. The attack works by evaluating `grav|array` in page content, which accesses the raw DI container and reveals redacted data.

Detection Guidance

Check Grav CMS version with: grep -r 'version' /path/to/grav/system/blueprints.yaml. If version is between 2.0.0 and 2.0.24, the system is vulnerable. Inspect Twig templates for unauthorized array filter usage in content. Monitor for unusual data exfiltration attempts in logs.

Impact Analysis

An attacker could exploit this to read sensitive site configuration data, including secrets like SMTP credentials, OAuth tokens, Redis passwords, and security settings. Since the payload is stored in page content, the exposed data is visible to all visitors, including anonymous users. This could lead to further attacks such as unauthorized access, data breaches, or service disruption.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR and HIPAA due to unauthorized exposure of sensitive data. GDPR requires protection of personal data, while HIPAA mandates safeguarding protected health information. A breach of credentials or configuration secrets could result in regulatory penalties, legal liabilities, and reputational damage for organizations using vulnerable Grav versions.

Mitigation Strategies

Upgrade Grav CMS to version 2.0.25 or later immediately. Disable Twig processing in content and modular pages if not required. Review exposed configuration files for compromised credentials and rotate all secrets. Implement network monitoring for unusual outbound data transfers.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-100668. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart