getgrav/grav

CVE-2026-44738

CVE-2026-44738 is a high-severity security vulnerability in getgrav/grav (composer), affecting versions <= 2.0.0-rc.1. It is fixed in 2.0.0-rc.2.

Key facts
CVSS score
7.7
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
getgrav/grav
Fixed in
2.0.0-rc.2
Disclosed
2026

Summary

Summary The Twig sandbox allow-list permits any user with the admin.pages role to call config.toArray() from within a page body, dumping the entire merged site configuration, including all plugin secrets (SMTP passwords, AWS keys, OAuth client secrets, API tokens), into the rendered HTML. No administrator privileges are required. Details The Twig sandbox allow-list in system/config/security.yaml explicitly permits Config::toArray() for the Grav\Common\Config\Config class: The config object, which holds the full merged configuration tree including every key under plugins., is injected into every sandboxed render in system/src/Grav/Common/Twig/Twig.php (line 292): Any editor with admin.pages can save a page with process.twig: true in the frontmatter and the following payload in the body: When the page is rendered, the full config tree is dumped as JSON in the HTML, including all plugin secrets stored under user/config/plugins/.yaml. PoC Impact Any user with the editor role (admin.pages) can exfiltrate all plugin credentials stored in the site configuration without any administrator privileges. Affected secrets include SMTP passwords, AWS access/secret keys, OAuth client secrets, reCAPTCHA keys, and any API token stored in plugin YAML config. Each extracted credential independently compromises the connected service.

Impact

Severity and exposure

CVE-2026-44738 has a CVSS score of 7.7 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (2.0.0-rc.2). Upgrading removes the vulnerable code path.

Affected versions

composer

  • getgrav/grav (<= 2.0.0-rc.1)

Security releases

  • getgrav/grav → 2.0.0-rc.2 (composer)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-44738 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-44738 is reachable in your applications. Get a demo

Remediation advice

Upgrade getgrav/grav to 2.0.0-rc.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-44738

What is CVE-2026-44738?

CVE-2026-44738 is a high-severity security vulnerability in getgrav/grav (composer), affecting versions <= 2.0.0-rc.1. It is fixed in 2.0.0-rc.2.

How severe is CVE-2026-44738?

CVE-2026-44738 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of getgrav/grav are affected by CVE-2026-44738?

getgrav/grav (composer) versions <= 2.0.0-rc.1 is affected.

Is there a fix for CVE-2026-44738?

Yes. CVE-2026-44738 is fixed in 2.0.0-rc.2. Upgrade to this version or later.

Is CVE-2026-44738 exploitable, and should I be worried?

Whether CVE-2026-44738 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-44738 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-44738?

Upgrade getgrav/grav to 2.0.0-rc.2 or later.

Stop the waste.
Protect your environment with Kodem.