Quick answers
- Is CVE-2026-53631 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53631 being exploited in the wild.
- How severe is CVE-2026-53631?
- Informational severity, published 4 November 2026.
- Which products and versions are affected?
- GLPI Project GLPI 0.83 to 10.0.26; 11.0.0 to 11.0.8.
- Is there a fix for CVE-2026-53631?
- Yes: fixed in 10.0.27, 11.0.9. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53631 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-53631?
- Check whether you run GLPI Project GLPI 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: 10.0.27, 11.0.9
Technical details
An authorization bypass vulnerability exists in GLPI's permission checks for visibility criteria on knowledge base items, reminders, and RSS feeds. Authenticated users could submit crafted POST requests to modify visibility settings without proper authorization validation. The fix adds explicit permission checks (CREATE validation) in the form handlers before applying visibility changes.
Affected products
- GLPI Project GLPI 0.83 to 10.0.26; 11.0.0 to 11.0.8
Timeline
- 2026-11-04: disclosed