How to Fix CVE-2026-26001: GLPI Inventory Plugin has SQL Injection on dropdown_calendar Report
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-33952: Critical Vulnerability in FreeRDP — Critical Vulnerability in FreeRDP
- How to Fix CVE-2026-25319: Critical Vulnerability in Zita Elementor Site Library — Critical Vulnerability in Zita Elementor Site Library
- How to Fix CVE-2026-3300: Everest Forms Pro <= 1.9.12 - Unauthenticated Remote Code Execution via Calculation Field , Everest Forms Pro <= 1.9.12 - Unauthenticated Remote Code Execution via Calculation Field
- How to Fix CVE-2026-26031: Access Control Bypass in lms , Access Control Bypass in lms
- How to Fix CVE-2026-21686: Input Validation Flaw in iccDEV , Input Validation Flaw in iccDEV
*By Sai Kiran Pandrala*
| Severity | CVSS 7.1, High |
|---|---|
| Actively exploited? | No |
| Affected | Glpi-project glpi-inventory-plugin (< 1.6.6) |
| Fixed in | 1.6.6 |
| Type (CWE) | CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') |
What is CVE-2026-26001?
The GLPI Inventory Plugin handles network discovery, inventory, software deployment, and data collection for GLPI agents. Prior to 1.6.6, non sanitized user input can lend to an SQL injection from reports, with adequate rights. This vulnerability is fixed in 1.6.6.
In practical terms, a successful attacker gets SQL injection that can read or modify the backing database. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.
Am I affected?
You're affected if you run Glpi-project glpi-inventory-plugin at any version in the Affected row above. Use these probes to find your installed build:
# Confirm the installed version via your package manager
dpkg -l | grep -i glpi-inventory-plugin # Debian/Ubuntu
rpm -qa | grep -i glpi-inventory-plugin # RHEL/CentOS/Rocky
How to fix CVE-2026-26001
The primary fix is to upgrade to the patched build listed in the Fixed in row above (1.6.6). Pick the platform that matches your install and run the commands below.
Linux (Ubuntu / Debian)
sudo apt-get update
sudo apt-get install --only-upgrade glpi-inventory-plugin
# Confirm the installed version meets or exceeds 1.6.6
dpkg -s glpi-inventory-plugin | grep ^Version
Linux (RHEL / CentOS / Rocky)
sudo dnf upgrade --security glpi-inventory-plugin -y
rpm -q glpi-inventory-plugin
Windows (PowerShell, admin)
# Try winget first
winget upgrade --id 'Glpi-project.glpi-inventory-plugin' --silent --accept-source-agreements --accept-package-agreements
# If winget does not know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\glpiinventoryplugin-1.6.6.msi" -ArgumentList '/qn /norestart' -Wait
PowerShell script (Windows) - detect, back up, upgrade, verify, log
# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\glpiinventoryplugin-Patch-CVE-2026-26001.log"
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Tee-Object -FilePath $log -Append }
Write-Log "Starting CVE-2026-26001 remediation for Glpi-project glpi-inventory-plugin"
# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
Where-Object { $_.Name -like '*glpi-inventory-plugin*' } |
Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"
if (-not $installed) {
Write-Log "Product not installed on this host; nothing to do."
return
}
if ([version]$installed -ge [version]'1.6.6') {
Write-Log "Already at fixed version $installed; no action needed."
return
}
# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\glpiinventoryplugin-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
# Adjust the source path to match your install
$src = "$env:ProgramFiles\Glpi-project\glpi-inventory-plugin"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"
# 3. Apply the patched installer (place the verified file on a share or staging path)
$installer = "$env:TEMP\glpiinventoryplugin-1.6.6.msi"
if (-not (Test-Path $installer)) {
throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"
# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
Where-Object { $_.Name -like '*glpi-inventory-plugin*' } |
Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'1.6.6') {
Write-Log "SUCCESS: now at $verify (>= 1.6.6)"
} else {
Write-Log "FAILURE: still at $verify after install"
exit 1
}
Bash script (Linux) - detect, back up, upgrade, verify, log
#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/glpi-inventory-plugin-patch-cve-2026-26001.log
log() { echo "$(date -Iseconds) $*" | tee -a "$LOG"; }
log "Starting CVE-2026-26001 remediation for Glpi-project glpi-inventory-plugin"
# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s glpi-inventory-plugin >/dev/null 2>&1; then
CURRENT=$(dpkg-query -W -f='${Version}' glpi-inventory-plugin)
PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q glpi-inventory-plugin >/dev/null 2>&1; then
CURRENT=$(rpm -q --queryformat '%{VERSION}' glpi-inventory-plugin)
PKG_MGR=dnf
else
log "glpi-inventory-plugin not installed via apt or rpm; check your package manager or vendor instructions."
exit 0
fi
log "Detected: glpi-inventory-plugin=$CURRENT (manager=$PKG_MGR)"
# 2. Backup config
BACKUP=/var/backups/glpi-inventory-plugin-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/glpi-inventory-plugin /etc/${pkg%%-*} ; do
[ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done
# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
sudo apt-get update -y
sudo apt-get install --only-upgrade -y glpi-inventory-plugin
else
sudo dnf upgrade --security -y glpi-inventory-plugin
fi
# 4. Verify
if [ "$PKG_MGR" = apt ]; then
NEW=$(dpkg-query -W -f='${Version}' glpi-inventory-plugin)
else
NEW=$(rpm -q --queryformat '%{VERSION}' glpi-inventory-plugin)
fi
log "After upgrade: $NEW"
# Optionally compare against 1.6.6 with dpkg --compare-versions or sort -V
log "Done. Restart the affected service if the package install did not."
If you can't patch immediately
These are runnable hardening commands. They reduce blast radius but they're not a replacement for the vendor patch.
Block obvious SQL injection patterns with a WAF rule
# ModSecurity / OWASP CRS-style rule
SecRule ARGS "@rx (?i)(union(.|\n)+?select|select(.|\n)+?from|insert(.|\n)+?into)" \
"id:900100,phase:2,deny,log,msg:'SQLi pattern blocked'"
How to verify the fix worked
Run the version probe again and confirm the running build matches the Fixed in row above.
# Confirm the running build matches the patched version listed by the vendor
# Example for Linux package installs:
dpkg -l | grep -i "glpi-inventory-plugin" # Debian/Ubuntu
rpm -qa | grep -i "glpi-inventory-plugin" # RHEL/CentOS/Rocky
Expected output: the package version should meet or exceed 1.6.6.
Then re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-26001 has cleared. Sweep your logs for the indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.
Frequently asked questions
Is CVE-2026-26001 being actively exploited?
Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.
How severe is CVE-2026-26001?
CVSS rates it 7.1 (High). Use that score to set your patch priority next to the other items in your queue.
Do I have to take glpi-inventory-plugin offline to apply the patch?
It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.
What if my vulnerability scanner still flags CVE-2026-26001 after I patch?
Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.
References
- Official vendor advisory: https://github.com/glpi-project/glpi-inventory-plugin/security/advisories/GHSA-gp4r-m42c-wvgx
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26001
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
*Written by Sai Kiran Pandrala on 2026-05-25. Sourced from the official vendor advisory, the NVD record, and the CISA KEV listing. Always confirm against the vendor advisory before applying changes in production.*