Is CVE-2026-56700 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-56700 being exploited in the wild.

How severe is CVE-2026-56700?

Critical severity, with a CVSS score of 9.8, published 30 June 2026.

Which products and versions are affected?

Grav before 2.0.0-beta.2; getgrav/grav (Packagist) ECOSYSTEM:introduced=0,fixed=2.0.0-beta.2.

Is there a fix for CVE-2026-56700?

Yes. getgrav/grav (Packagist): upgrade to 2.0.0-beta.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-56700 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-56700?

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.

CVE-2026-56700: Grav CMS multiple remote code execution vulnerabilities

CVE-2026-56700 · Severity: critical · CVSS 9.8 · Published 2026-06-30

Grav CMS, a popular content management system, contains multiple security flaws that could allow an attacker to take complete control of the server. These vulnerabilities stem from how the system handles internal data and administrative commands, potentially leading to unauthorized data access or full system compromise. Organizations using Grav should update to version 2.0.0-beta.2 or later to protect their operations and data.

Technologies: Grav, getgrav/grav (Packagist). Vendors: Grav, Packagist.

Quick answers

Is CVE-2026-56700 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56700 being exploited in the wild.
How severe is CVE-2026-56700?: Critical severity, with a CVSS score of 9.8, published 30 June 2026.
Which products and versions are affected?: Grav before 2.0.0-beta.2; getgrav/grav (Packagist) ECOSYSTEM:introduced=0,fixed=2.0.0-beta.2.
Is there a fix for CVE-2026-56700?: Yes. getgrav/grav (Packagist): upgrade to 2.0.0-beta.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-56700 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-56700?: 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-beta.2 or later
```
composer require getgrav/grav:^2.0.0-beta.2
```

Technical details

Grav CMS versions prior to 2.0.0-beta.2 contain five distinct RCE vectors. Three critical vulnerabilities involve unsafe PHP unserialize() calls in the JobQueue, FileCache, and Session components, where lack of class restriction allows for PHP object injection and gadget chain execution. An additional critical flaw in the InstallCommand component allows for OS command injection because branch, URL, and path parameters are passed to shell commands without proper escaping during git clone operations (requires admin privileges). Finally, a high-severity bypass in the Twig security blocklist allows for server-side template injection (SSTI). These issues are addressed in version 2.0.0-beta.2 through the implementation of HMAC-signed serialized envelopes, proper shell argument escaping, and an updated Twig sandbox.

Affected products

Grav Grav CMS before 2.0.0-beta.2

Identifiers

CVE-2026-56700
GHSA-vj3m-2g9h-vm4p

Timeline

2026-04-24: patched: Fixes applied to the 2.0 branch by maintainers.
2026-04-27: advisory: GitHub Security Advisory published.
2026-06-30: disclosed: NVD publication and VulnCheck advisory.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.