Skip to main content
Mallory
CriticalVulnerability

CVE-2026-26263: Unauthenticated time-based blind SQL injection in GLPI Search engine

Published Apr 6, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS8.4%95th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Glpi-Project
IdentifiersCVE-2026-26263CWE-89 · Improper Neutralization of Special…

CVE-2026-26263 is an unauthenticated time-based blind SQL injection vulnerability in the GLPI Search engine. It affects GLPI versions 11.0.0 through before 11.0.6. The issue allows attacker-controlled input to influence SQL queries in the Search functionality, enabling blind inference through time-delay techniques without requiring authentication. The vulnerability is fixed in GLPI 11.0.6.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote unauthenticated attacker to execute time-based blind SQL injection against the GLPI Search engine. Based on the provided classification and CVSS context, this can result in unauthorized access to database-resident information and potentially modification of data and service impact, with high confidentiality, integrity, and availability impact.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure of the GLPI Search engine to untrusted networks, restrict public access to the application, and apply compensating controls such as WAF rules or request filtering for suspicious search-related parameters. These are interim measures only; the definitive fix is upgrading to 11.0.6 or later.

Remediation

Patch, then assume compromise.

Upgrade GLPI to version 11.0.6 or later, which fixes this vulnerability.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Glpi-ProjectGlpiapplication
FAQ

Frequently asked questions

Is CVE-2026-26263 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-26263 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-26263?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-26263.
Is there a patch for CVE-2026-26263?
Upgrade GLPI to version 11.0.6 or later, which fixes this vulnerability.
What products are affected by CVE-2026-26263?
Glpi-Project Glpi.
How severe is CVE-2026-26263?
CVE-2026-26263 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 8.4% (95th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.