Quick answers
- Is CVE-2026-100668 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100668 being exploited in the wild.
- How severe is CVE-2026-100668?
- Medium severity, with a CVSS score of 6.5, published 26 September 2026.
- Which products and versions are affected?
- Getgrav Grav 2.0.0 through 2.0.24.
- Is there a fix for CVE-2026-100668?
- A patch was published on 2026-09-26: Grav 2.0.25 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100668 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-100668?
- Check whether you run Getgrav 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.
Technical details
The array filter lacks the needs_is_sandboxed guard present in similar filters and calls toArray() or (array) cast without consulting the sandbox method allowlist. An attacker with content authoring permissions can invoke grav|array to access the raw Pimple dependency injection container's $values array, then cast the Config object to retrieve the entire unredacted configuration tree. The vulnerability affects Grav 2.0.0–2.0.24; version 2.0.25 applies the sandbox guard to the array and yaml filters.
Affected products
- getgrav Grav 2.0.0 through 2.0.24
Timeline
- 2026-09-09: disclosed
- 2026-09-26: advisory
- 2026-09-26: patched: Grav 2.0.25 released