Quick answers
- Is CVE-2026-44738 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44738 being exploited in the wild.
- How severe is CVE-2026-44738?
- High severity, with a CVSS score of 7.7, published 11 May 2026.
- Which products and versions are affected?
- Grav < 2.0.0-rc.2, <= 2.0.0-rc.1; getgrav/grav (Packagist) <= 2.0.0-rc.1, ECOSYSTEM:introduced=0,fixed=2.0.0-rc.2.
- Is there a fix for CVE-2026-44738?
- Yes. getgrav/grav (Packagist): upgrade to 2.0.0-rc.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44738 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-44738?
- 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.
How to fix
- getgrav/grav (Packagist): upgrade to 2.0.0-rc.2 or later
composer require getgrav/grav:^2.0.0-rc.2
Technical details
A vulnerability exists in Grav's Twig sandbox configuration where the 'Config::toArray()' method is explicitly permitted in the security allow-list. Users with 'admin.pages' privileges can create or edit a page, enable Twig processing in the frontmatter, and use a Twig payload to dump the entire merged site configuration into the rendered HTML. This configuration object contains sensitive plugin secrets, including SMTP passwords, AWS keys, and OAuth tokens. The issue is rooted in 'system/config/security.yaml' and affects versions up to 2.0.0-rc.1. A patch is available in version 2.0.0-rc.2.
Affected products
- getgrav Grav <= 2.0.0-rc.1
Identifiers
- CVE-2026-44738
- GHSA-j274-39qw-32c9
Timeline
- 2026-05-09: disclosed
- 2026-05-11: advisory: NVD publication date
- 2026-05-13: patched: GitHub Advisory reviewed and updated