Quick answers
- Is CVE-2026-53629 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53629 being exploited in the wild.
- How severe is CVE-2026-53629?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- GLPI Project GLPI 9.4.0 to 10.0.25, 11.0.0 to 11.0.7.
- Is there a fix for CVE-2026-53629?
- 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-53629 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-53629?
- 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.
Technical details
A SQL injection vulnerability exists in the history tab endpoint that fails to properly sanitize user-controlled input passed through URL parameters before incorporating them into database queries. An attacker with READ privileges on logs can craft a specially-crafted URL to inject arbitrary SQL commands. The vulnerability affects versions 9.4.0 through 10.0.25 and 11.0.0 through 11.0.7; patches are available in versions 10.0.26 and 11.0.8.
Affected products
- GLPI Project GLPI 9.4.0 to 10.0.25, 11.0.0 to 11.0.7
Timeline
- 2026-09-25: disclosed