Live › technique › TECH-202610-glpi-agent-remote-code-execution-via-rogue-glpi-server-using
Go to dashboardFenrisk research (2026-10-20) with a newly public tool, GLPwnIou. GLPI Agent before 1.8, and agents upgraded from before 1.8, ask the server for inventory/deploy tasks by default and run them as SYSTEM/root, even when the server does not use deploy. Before, HTTPS with certificate checking stopped a fake server. With an ESC17-vulnerable AD CS template (Server Authentication EKU plus Enrollee Supplies Subject), an attacker in the domain can get a valid certificate for the GLPI server's name. They then put themselves in the middle (mitm6, ARP spoofing, or a stale or editable DNS record) and push commands or binaries to every agent that connects. At risk: Active Directory environments running GLPI Agent with a misconfigured AD CS. Proof of concept and pentest tool; no in-the-wild use reported.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 15:07 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| GLPI Agent | – | – | – |
| GLPI | – | – | – |
| Active Directory Certificate Services | – | – | – |
GLPI Agent version below 1.8, or installed before 1.8 and later upgraded, with the deploy task active; AD CS templates allowing Server Authentication plus Enrollee Supplies Subject to low-privileged users; CA events 4886/4887 for the GLPI server name from an unexpected requester; glpi-agent spawning cmd.exe/powershell or writing C:\Windows\Temp\pwned.fenrisk; deploy responses with ID 0fae2958-24d5-0651-c49c-d1fec1766af6 and no usual GLPI/PHP headers
Lock down AD CS Server Authentication templates (limit who can enroll, remove Enrollee Supplies Subject) and audit certificate requests; turn off the deploy task on agents that do not need it (agents upgraded from before 1.8 keep it on); enforce HTTPS with strict checking or pinning to the GLPI server certificate; disable IPv6 where unused to block mitm6, and watch DNS changes for the GLPI host
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
This page as .md · .json · in your agent: get_signal("TECH-202610-glpi-agent-remote-code-execution-via-rogue-glpi-server-using")