Quick answers
- Is CVE-2026-116019 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116019 being exploited in the wild.
- How severe is CVE-2026-116019?
- High severity, with a CVSS score of 8.8, published 24 October 2026.
- Which products and versions are affected?
- Grav 2.0.15 through 2.2.12.
- Is there a fix for CVE-2026-116019?
- Yes: fixed in 2.2.13. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116019 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116019?
- Check whether you run Grav 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
- Fixed in: 2.2.13
Technical details
An allowlist bypass in Grav's Blueprint data processing allows attackers to invoke arbitrary public static methods by relocating data-*@ directives through unset-name@ or integer keys in Flex form overrides. The vulnerability exists in the deepMerge() routine which fails to properly restrict relocated fields, allowing page editors to craft frontmatter that calls methods such as Folder::delete() or Utils::download(). Authentication as a page editor is required to exploit this flaw.
Affected products
- Grav Grav 2.0.15 through 2.2.12
Timeline
- 2026-10-24: disclosed