The GLPI project shipped a pair of security releases on 12 November 2026 — 12.0.2 and 11.0.13. The release notes for both list the same five fixes, every one of them rated High.
That is two weeks after the previous batch, 12.0.1 and 11.0.12 of 28 October. Branch 10 again got nothing: its last version remains 10.0.28, released on 30 September 2026.
The list of fixes
It is identical in both releases:
- Privilege escalation via the legacy API (version v1).
- OAuth server consent bypass.
- Account takeover via an embedded dashboard.
- Stored XSS in document downloads, through filenames written via the API.
- Account takeover via password-reset hijacking.
The announcement lists four, the release notes five
The project's blog post about these releases names only the first four. The fifth — account takeover via password-reset hijacking — appears in the release notes for both 12.0.2 and 11.0.13 on GitHub, but not in the blog post (as of 16 November 2026). Anyone building a patch plan should work from the release notes; the web summary is incomplete in this case.
Which parts of GLPI the fixes touch
The project has again published no exploitation conditions. The titles do, however, point at four specific features, and for each of them it takes a few minutes to establish whether an installation uses it at all:
- The legacy v1 API — in the configuration under the API tab, together with API clients, the app token and IP-based access filtering.
- OAuth clients — a separate item in the configuration. Watch out for agents: if inventory authentication is set to OAuth client credentials, the GLPI agent connects to the server with the ID and secret of an OAuth client.
- Dashboard sharing — the share icon on a dashboard offers a direct link, an iframe embed, and sharing with profiles, entities, users and groups.
- Password reset — the link on the login page appears only when notifications are enabled, and it is switched off by deactivating the forgotten-password notification. A reset link stays valid for 24 hours.
This list sets priority, not scope. Until the project describes the vectors, the fact that an installation shares no dashboards is not grounds for concluding that the fix does not apply to it.
No advisories yet
As of 16 November 2026 there are no advisories and no CVE identifiers for the 12 November batch, nor yet for the 28 October one. The newest GLPI advisories on GitHub are dated 2 November and cover the 11.0.10 and 10.0.28 releases of 30 September.
What to do
- Move from any 12.0.x to 12.0.2, and from any 11.0.x to 11.0.13. The branch does not change.
- Back up the database and the attachment directories before upgrading, and have a tested way back.
- Run the database update (
php bin/console db:update) and read its output. - After deployment, test the integrations that go through the API and OAuth — including inventory coming in from agents.
- Check plugins and custom changes that touch the API or authentication.
- Record the change, with the deployment date and the reason.
Branch 12 is five weeks past its stable release and has taken two security patches in that time — 12.0.1 and 12.0.2. Anyone who migrated right after 7 October has had two maintenance windows since. A patching window for GLPI is worth putting in the calendar ahead of time, rather than opening one ad hoc after each announcement.