Quick answers
- Is CVE-2026-53625 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53625 being exploited in the wild.
- How severe is CVE-2026-53625?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- GLPI Project GLPI 0.70 to 10.0.25, 11.0.0 to 11.0.7.
- Is there a fix for CVE-2026-53625?
- A patch was published on 2026-09-25: Fixed in GLPI 10.0.26 and 11.0.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53625 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-53625?
- 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 privilege escalation vulnerability exists in GLPI's user management API where the authtype parameter can be manipulated by authenticated technicians to modify another user's authentication method. Under SSO or legacy API REST configurations, this allows changing a super-administrator's authentication method to enable account takeover. The vulnerability affects versions 0.70 through 10.0.25 and 11.0.7.
Affected products
- GLPI Project GLPI 0.70 to 10.0.25, 11.0.0 to 11.0.7
Timeline
- 2026-09-25: disclosed
- 2026-09-25: patched: Fixed in GLPI 10.0.26 and 11.0.8