PACKAGIST · JULY 2026 · EARLY WARNING

Grav 2.0.4 Remote Code Execution Vulnerability Under Investigation

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
CVE-2026-65008Severity: CRITICAL

Grav 2.0.4 is under investigation for a critical remote code execution vulnerability that affects versions prior to 2.0.7.

What happened

Grav 2.0.4 reportedly contains a remote code execution vulnerability in the Blueprint::dynamicData() method, tracked as CVE-2026-65008. This vulnerability allows an authenticated attacker with admin.pages or api.pages.write permissions to execute arbitrary commands as the web-server user. The vulnerability is present in versions prior to 2.0.7. It is recommended to upgrade to Grav 2.0.7 or later to mitigate the risk.

The vulnerability arises from the improper handling of callable strings and arguments in the Blueprint::dynamicData() method. An authenticated attacker can exploit this by planting a malicious callable directive in a page, which then executes as the web-server user when the page is accessed.

For more detailed information, consult the primary sources: [CVE-2026-65007](https://nvd.nist.gov/vuln/detail/CVE-2026-65007) and [CVE-2026-65008](https://nvd.nist.gov/vuln/detail/CVE-2026-65008).

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If grav is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats