Quick answers
- Is CVE-2026-109325 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109325 being exploited in the wild.
- How severe is CVE-2026-109325?
- High severity, with a CVSS score of 7.5, published 12 October 2026.
- Which products and versions are affected?
- Grav 2.0.22 through 2.1.6.
- Is there a fix for CVE-2026-109325?
- Yes: fixed in 2.1.7, 2.0.26. Until then: Disable the Clockwork profiler or restrict network access to the /__clockwork endpoint to trusted hosts only. Ensure X-Clockwork-Auth tokens are properly configured and validated on every profiler data read request. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109325 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-109325?
- 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, 2.0.26
Disable the Clockwork profiler or restrict network access to the /__clockwork endpoint to trusted hosts only. Ensure X-Clockwork-Auth tokens are properly configured and validated on every profiler data read request.
Technical details
The Clockwork profiler endpoint runs before user authorization and checks the X-Clockwork-Auth header, but unconditionally accepts requests from loopback TCP peers (127.0.0.1). Behind a same-host HTTP proxy, all external client requests appear to originate from the proxy's loopback address, defeating the authentication check. The vulnerability requires Clockwork to be enabled and a same-host HTTP proxy; the default FastCGI topology is unaffected.
Affected products
- Grav Grav 2.0.22 through 2.1.6
Timeline
- 2026-09-23: disclosed
- 2026-10-12: advisory