Quick answers
- Is CVE-2026-109324 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109324 being exploited in the wild.
- How severe is CVE-2026-109324?
- Medium severity, with a CVSS score of 6.5, published 12 October 2026.
- Which products and versions are affected?
- Grav < 2.1.7.
- Is there a fix for CVE-2026-109324?
- Yes: fixed in 2.1.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109324 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-109324?
- 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.1.7
Technical details
The vulnerability exists in Grav's image transform handling for Twig and Markdown, where GD or Imagick decoders process the full source raster dimensions before resizing, without checking against the max_pixels limit. An authenticated media author uploads a highly compressed image; when any user references a transform that requires decoding, the uncompressed source exhausts memory. The issue affects Grav 2.x through 2.1.6; patched in 2.1.7 by validating source dimensions before adapter initialization.
Affected products
- Grav Grav < 2.1.7
Timeline
- 2026-09-23: disclosed: GitHub Security Advisory published
- 2026-10-12: advisory: NVD entry and CVE-2026-109324 published