Quick answers
- Is CVE-2026-49470 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49470 being exploited in the wild.
- How severe is CVE-2026-49470?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- GLPI Project GLPI 11.0.0 through 11.0.7.
- Is there a fix for CVE-2026-49470?
- A patch was published on 2026-06-24: Version 11.0.8 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49470 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-49470?
- 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
The time-based one-time password (TOTP) verification endpoint in GLPI lacks rate limiting on failed submission attempts. An attacker with valid primary credentials can brute-force the six-digit TOTP value by submitting unlimited guesses against the MFA verification endpoint. The vulnerability requires prior compromise of the user's username and password but enables bypass of the second authentication factor; it is patched in version 11.0.8.
Affected products
- GLPI Project GLPI 11.0.0 through 11.0.7
Timeline
- 2026-09-25: disclosed
- 2026-06-24: patched: Version 11.0.8 released with fix