PatchSiren cyber security CVE debrief
CVE-2026-76846 getgrav CVE debrief
CVE-2026-76846 is a high-severity vulnerability in Grav, a content management system, with a CVSS score of 8.7. The vulnerability occurs due to an incomplete default denylist in the Twig sandbox configuration, allowing attackers with page-edit permission to retrieve sensitive system configuration values using Twig templates when config_access is enabled. This could lead to potential sensitive information disclosure. The vulnerability can be mitigated by applying the patch to upgrade Grav to version 2.0.16 or later, restricting page-edit permissions, and monitoring system configuration access. Affected Grav users and administrators should prioritize patching and take necessary actions to prevent potential sensitive information disclosure via Twig sandbox misconfiguration. The CVE record was published on 2026-08-25T02:16:51.743Z and has not been modified since then. The NVD entry is currently Deferred.
- Vendor
- getgrav
- Product
- grav
- CVSS
- HIGH 8.7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-25
- Original CVE updated
- 2026-08-31
- Advisory published
- 2026-08-25
- Advisory updated
- 2026-08-31
Who should care
Grav users and administrators, especially those with page-edit permissions enabled, should be aware of this vulnerability and take necessary actions to prevent potential sensitive information disclosure.
Technical summary
CVE-2026-76846 is a high-severity vulnerability in Grav, a content management system. The vulnerability has a CVSS score of 8.7 and occurs due to an incomplete default denylist in the Twig sandbox configuration. This allows attackers with page-edit permission to retrieve sensitive system configuration values using Twig templates when config_access is enabled. The vulnerability can be mitigated by applying the patch to upgrade Grav to version 2.0.16 or later, restricting page-edit permissions, and monitoring system configuration access.
Defensive priority
Grav users should prioritize patching to prevent potential sensitive information disclosure via Twig sandbox misconfiguration.
Recommended defensive actions
- Apply the patch to upgrade Grav to version 2.0.16 or later.
- Restrict page-edit permissions to trusted users.
- Monitor system configuration access and usage.
- Consider disabling config_access if not required.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
Evidence notes
The CVE-2026-76846 record indicates that Grav before version 2.0.16 has an incomplete default denylist in the Twig sandbox configuration. This allows attackers with page-edit permission to access system configuration secrets using config.get() or config.toArray() in Twig templates when config_access is enabled. Official sources include the CVE Program and NIST NVD, which provide vulnerability metadata and assessments.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-76846 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-76846
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-76846 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-76846
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/getgrav/grav/security/advisories/GHSA-xjw5-q542-3vmr
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/grav-before-information-disclosure-via-twig-sandbox
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.