Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- High severity, with a CVSS score of 7.5, published 25 August 2026.
- Which products and versions are affected?
- Grav <2.0.16; getgrav/grav (Packagist) < 2.0.16.
- Is there a fix for This vulnerability?
- A patch was published on 2026-08-10: Version 2.0.16 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network.
- Am I affected?
- Check whether you run Grav or getgrav/grav (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Grav versions before 2.0.16 ship an incomplete default denylist in the Twig sandbox configuration (twig_sandbox.config_denied_paths in system/config/security.yaml). The denylist includes 'plugins', 'streams', 'security', 'backups', and 'scheduler' but omits 'system', which contains sensitive values like system.cache.redis.password. When config_access is enabled (a non-default setting intended to safely expose low-sensitivity values), any user with page-edit permission can call config.get() or config.toArray() in Twig templates to retrieve secrets. This is a follow-up gap to the fix for GHSA-j274-39qw-32c9. The patch in version 2.0.16 adds 'system' to the denylist.
Affected products
- Grav Grav <2.0.16
Timeline
- 2026-08-25: disclosed
- 2026-08-10: patched: Version 2.0.16 released