Quick answers
- Is CVE-2026-117604 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-117604 being exploited in the wild.
- How severe is CVE-2026-117604?
- High severity, with a CVSS score of 7.5, published 27 October 2026.
- Which products and versions are affected?
- Getgrav Grav 1.7.53.3 before 1.7.53.6.
- Is there a fix for CVE-2026-117604?
- Yes: fixed in 1.7.53.6. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-117604 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-117604?
- 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.
How to fix
- Fixed in: 1.7.53.6
Technical details
The Debugger::isDebuggerRequestAuthorized() method incorrectly trusts the REMOTE_ADDR header to verify requests originating from localhost, allowing bypass of token authentication. When Grav runs behind a same-host reverse proxy, remote requests appear as loopback traffic, enabling attackers to access /__clockwork/ profiler records without credentials. The vulnerability requires no user interaction and is exploitable over the network in reverse-proxy environments.
Affected products
- Getgrav Grav 1.7.53.3 before 1.7.53.6
Timeline
- 2026-10-27: disclosed