Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Critical · CVSS 9.1

How to Fix CVE-2026-26026: glpi (Bundle Sibling)

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

⚡ At a glance
SeverityCVSS 9.1, Critical
Actively exploited?No
AffectedGlpi-project glpi (>= 11.0.0, < 11.0.6)
Fixed inSame patched build as CVE-2026-25932
Type (CWE)CWE-94: CWE-94: Improper Control of Generation of Code ('Code Injection')

CVE-2026-26026 is a sibling vulnerability in the same Glpi-project glpi advisory bundle as CVE-2026-25932. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-26026 matches the primary write-up.

What is different about CVE-2026-26026?

GLPI is a free asset and IT management software package. From 11.0.0 to before 11.0.6, template injection by an administrator lead to RCE. This vulnerability is fixed in 11.0.6.

Impact is consistent with the bundle: compromise of the affected component as described in the vendor advisory. The patched build closes every code path in the advisory in one update.

How to fix CVE-2026-26026

Apply the patched build per the primary write-up: How to Fix CVE-2026-25932.

For a quick check, confirm the running version of glpi:


# Confirm the installed version via your package manager
dpkg -l | grep -i glpi   # Debian/Ubuntu
rpm -qa | grep -i glpi   # RHEL/CentOS/Rocky

Frequently asked questions

Is CVE-2026-26026 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-26026?

CVSS rates it 9.1 (Critical). Use that score to set your patch priority alongside the other items in your queue.

Do I have to take glpi 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-26026 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


*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Glpi-project glpi advisory bundle. Full procedure at how-to-fix-cve-2026-25932.*