Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-p597-crqc-m349

Grav: The system, site, and theme Twig variables bypass the content sandbox entirely and are never covered by config_denied_paths

CVSS 7.1 HighEPSS 0.0041 · 35th percentile

Published by the GitHub Advisory Database at 17 Sept 2026, 20:25 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
getgrav/gravPackagist<2.0.162.0.16
Identifiers
GHSA-p597-crqc-m349 · CVE-2026-72698 · PKSA-wz98-fgrh-3wq2
Weakness (CWE)
CWE-200
Tags
Published
17 Sept 2026
Updated
17 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Grav (getgrav/grav, Packagist) versions before 2.0.16 expose the raw system, site, and theme configuration arrays inside the sandboxed Twig render used for page content, so Twig's sandbox policy and the config_denied_paths setting do not restrict them. An attacker who can edit page content with Twig processing enabled (or inject Twig into page content) could read these values, including secrets stored under them, even when the config variable is disabled. Upgrade to Grav 2.0.16 or later, which is the listed fixed version.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.1 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0041, the 35th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:55 UTC First seen by agentprime
  2. 31 Oct 2026, 13:55 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.