Quick answers
- Is CVE-2026-47688 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47688 being exploited in the wild.
- How severe is CVE-2026-47688?
- High severity, with a CVSS score of 8.2, published 21 July 2026.
- Which products and versions are affected?
- FOGProject FOG Project < 1.5.10.1832, < 1.6.0-beta.2313.
- Is there a fix for CVE-2026-47688?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-47688 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-47688?
- Check whether anything you run is named in the advisory. 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
A missing authorization check (CWE-862) in the FOG management interface allows unauthenticated access to the 'client' node endpoint. The 'FOGPageManager::render()' method dynamically invokes sub-methods based on GET parameters without verifying the user's identity or permissions. Specifically, the 'clearAES' and 'clearPMTasks' methods in the 'FOGPage' class are exploitable because they operate on global variables ($id and $groupid) rather than initialized objects. An attacker can send a single HTTP GET request to wipe 'pub_key', 'sec_tok', and 'sec_time' for hosts or destroy power management tasks for groups. This breaks encrypted FOG Client communication and destroys scheduled tasks. The issue is fixed in versions 1.5.10.1832 and 1.6.0-beta.2313.
Affected products
- FOGProject FOG Project < 1.5.10.1832, < 1.6.0-beta.2313
Timeline
- 2026-05-19: advisory: GitHub Security Advisory published by FOGProject
- 2026-07-21: disclosed: CVE published to NVD