CVE-2026-26026
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGLPI 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGLPI versions 11.0.0 through 11.0.5 contain a template injection vulnerability that allows authenticated administrators to achieve remote code execution. The vulnerability was patched in version 11.0.6.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 11.0.0, < 11.0.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify GLPI installation versionLocate the version file in your GLPI installation (commonly version.php or similar in the root directory) or access the system information page in the GLPI admin panelAffected if The installed version is 11.0.0, 11.0.1, 11.0.2, 11.0.3, 11.0.4, or 11.0.5 (any version >= 11.0.0 and < 11.0.6)
-
Confirm administrator account accessCheck whether any user account with administrator privileges exists in the GLPI user management sectionAffected if Authenticated administrator accounts are present in the system
-
Verify template feature accessibilityNavigate to the GLPI administration panel and confirm whether the template management feature (or similar entity template configuration) is accessible to administrator usersAffected if The template functionality is available to administrator accounts in the web interface
You are affected if your GLPI version is 11.0.0 through 11.0.5 AND administrator accounts with access to the template feature exist in your environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped11.0.6
Upgrade GLPI to version 11.0.6 or later to remediate this vulnerability.
GLPI 11.0.6
- Back up the GLPI database and all files to ensure data can be recovered if issues occur
- Download GLPI version 11.0.6 from the official source (github.com/glpi-project/glpi)
- Replace the existing GLPI files with the new 11.0.6 files, preserving configuration and custom files if needed
- Run the GLPI upgrade script or navigate to the GLPI URL to complete the upgrade process
- Verify that the upgrade was successful by logging in and checking the GLPI version (should show 11.0.6)
- Test that normal GLPI functionality works as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26026 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26026 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data