Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-26026: Authenticated Template Injection RCE in GLPI

Published Apr 6, 2026 · Updated 16 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS7.2High · v3.1
EPSS12.0%96th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Glpi-Project
IdentifiersCVE-2026-26026CWE-1336 · Improper Neutralization of Special…

CVE-2026-26026 is a template injection vulnerability in GLPI, an asset and IT management application, affecting versions 11.0.0 through versions before 11.0.6. An authenticated administrator can exploit template processing to achieve remote code execution. 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 permits remote code execution, potentially compromising the confidentiality, integrity, and availability of the affected system. The assigned CVSS v3.1 vector indicates high impact across all three categories and a changed security scope.

Mitigation

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

Until the upgrade is completed, restrict GLPI administrative access to trusted users and protect administrative credentials against compromise. These controls reduce exposure but do not correct the template injection vulnerability.

Remediation

Patch, then assume compromise.

Upgrade affected GLPI installations to version 11.0.6 or a later release containing the fix.

Public exploits

Exploits

4 exploits validated by Mallory's analysis.

View more in app →
CVE-2026-26026-PoCSingle-file Bash exploit PoC targeting a GLPI web application. The script accepts a target IP/host, a form ID, and a command to execute; defaults are 176.16.74.57, form ID 6, and command id. It uses curl to fetch the application root page, stores cookies in /tmp/glpi_cookies.txt, extracts the _glpi_csrf_token from HTML, and authenticates with hardcoded default credentials glpi/glpi via /front/login.php. It then verifies login success by requesting /front/central.php. After authentication, the exploit sends a crafted request to /ajax/common.tabs.php with parameters pointing at /front/form/form.form.php, setting fn=shell_exec and a=<command>, which is the core remote code execution primitive. The script attempts to parse command output from returned HTML values and, if parsing fails, saves the raw response to /tmp/rce_response.html. Repository structure is minimal: one Bash script with no auxiliary files, indicating a straightforward operational PoC rather than a framework module or detection-only script.CEAarab · Disclosed Apr 22, 2026 · bash · web · networkOperationalCVE-2026-26026-PoCThe repository contains one Bash proof-of-concept, PoC.sh. It is a standalone operational exploit rather than a framework module. The script accepts a target IP/host, GLPI form ID, and shell command, defaulting to 176.16.74.57, form ID 6, and id. It establishes a session, extracts GLPI's CSRF token from the home page, attempts authentication with default glpi/glpi credentials, and verifies dashboard access. It then sends an authenticated request to ajax/common.tabs.php targeting Glpi\Form\Form and provides fn=shell_exec with the supplied command in a. The response is heuristically parsed for command output; otherwise it is retained locally for inspection. No specific CVE or GLPI version is identified in the code.wuyou6956-glitch · Disclosed Sep 30, 2026 · bash · network · webOperationalCVE-2026-26026_PoCThis is a three-file authenticated proof-of-concept repository for CVE-2026-26026 in GLPI Forms. Its primary executable, `POC_GLPI_Form_Dropdown_SSTI.py`, is a Python 3 Requests-based exploit that logs in, creates a Form, saves a Dropdown option containing a Twig expression, and renders the form's main tab with crafted GET parameters. The vulnerable double Twig compilation causes the expression to dispatch to PHP `shell_exec`, yielding arbitrary command execution and response-based output confirmation. The supplied command is configurable with `--cmd`; marker strings are used to reliably isolate command output. The exploit disables TLS certificate verification, supports a positional URL or `--target`, handles a single CSRF-token refresh retry, and can save the trigger response for debugging. `README.md` documents use and states that GLPI 11.0.6 patches the flaw. `docker-compose.yml` provisions MariaDB and GLPI 11.0.4, exposing GLPI on host port 8080, as a reproducible vulnerable lab. The repository contains one Python exploit, one Compose configuration, and documentation; it is a functional exploit rather than merely a detector.petriQore · Disclosed Oct 1, 2026 · python · yaml · web · networkOperationalCVE-2026-26026-GLPIThis is a standalone vulnerability research and manual exploitation repository, not a framework module or automated scanner. Its 17 files comprise eight PHP source snapshots, a Dockerfile, three supporting Docker/Xdebug configuration files, a corrective patch, two Markdown documents, a license, and .gitignore. The PHP sources contain embedded JavaScript and Twig. The source/11.0.5 and source/11.0.6 trees each contain the AJAX tab dispatcher, PhpExtension, AbstractQuestionTypeSelectable, and QuestionTypeDropdown. The complete application, dependencies, database contents, and referenced screenshots are absent. The documented attack stores a Twig expression in a Dropdown option. In the vulnerable rendering sequence, QuestionTypeDropdown appends HTML already rendered by its parent to a template string and compiles that combined string again. Attacker-controlled option text therefore becomes Twig source during the second render. PhpExtension exposes call(), which validates that a supplied value is callable and then invokes call_user_func_array(); this enables command execution when a callable such as shell_exec is selected through request parameters. The write-up reports id output identifying www-data and describes additional read-only command tests. These execution results are reported evidence, not independently reproduced here. The patch changes the parent-render result to a separate $parent variable and appends it only after rendering the child template, preventing re-compilation of the option HTML. GLPI 11.0.6 is included as the fixed comparison, while the write-up claims an affected range of 11.0.0 through versions before 11.0.6. Several supplied source files are truncated, limiting independent inspection of the complete rendering flow. The lab uses PHP 8.4, MariaDB 11.8, Mailpit, and trigger-based Xdebug. Its published ports are not explicitly bound to loopback, and its Dockerfile grants www-data unrestricted passwordless sudo; both are lab configuration risks distinct from the SSTI. No exfiltration destination, reverse-shell listener, destructive payload, or persistence mechanism is present. Repository reference and archive size were not supplied; the empty ref and zero size are unknown-value placeholders.PeaMatNgu · Disclosed Oct 29, 2026 · php · javascript · web · networkOperational
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-26026 exploited in the wild?
As of Nov 1, 2026, Mallory has no reports of CVE-2026-26026 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-26026?
Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2026-26026, the earliest disclosed Apr 22, 2026.
Is there a patch for CVE-2026-26026?
Upgrade affected GLPI installations to version 11.0.6 or a later release containing the fix.
What products are affected by CVE-2026-26026?
Glpi-Project Glpi.
How severe is CVE-2026-26026?
CVE-2026-26026 has a CVSS v3.1 score of 7.2 (High) and an EPSS score of 12.0% (96th percentile) as of Nov 1, 2026.
Activity feed

Recent activity

8 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 activity7Community discussion across Reddit, Mastodon, and other social sources.