CVE-2026-26263
Unauthenticated time-based blind SQLi in GLPI search (11.0.0–11.0.5); fixed in 11.0.6.
Is CVE-2026-26263 being exploited?
Not confirmed. CVE-2026-26263 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 8.3% probability of exploitation in the next 30 days.
How severe is CVE-2026-26263?
CVE-2026-26263 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-26263?
Yes. A fix has been recorded for CVE-2026-26263. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-26263 affect?
CVE-2026-26263 affects GLPI 11.0.0 - 11.0.5. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-26263?
Upgrade to 11.0.6; apply patch now.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote SQL injection enables data exfiltration via time-based queries; could access GLPI database.
Immediate action required
- affected>= 11.0.0 and < 11.0.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.