Skip to main content
VulnerabilityPublished

CVE-2026-53627: glpi · Missing Authorization

Affects glpiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.0 Medium : upgrade to 11.0.8 when convenient.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 11.0.8
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Upgrade glpi and glpi-project/glpi to 11.0.8.

Affected software

ProductAffectedFixed in
glpi-projectglpiAffected
  • >=11.0.0 <11.0.8
Fixed in
  • 11.0.8
GitHubglpi-project/glpipkg:github/glpi-project/glpiOther threatsAffected
  • >=11.0.0 <11.0.8
Fixed in
  • 11.0.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade GLPI to version 11.0.8 or later, where this missing authorization issue is fixed. No other mitigations are indicated or necessary once the official fix is applied.

Description

GLPI is a free asset and IT management software package. From 11.0.0 until 11.0.8, a low-privileged authenticated user can use the new API (v2) to perform update operations that the same user is normally forbidden to perform through the user interface. The API update flow does not consistently enforce the applicable authorization checks. This issue is fixed in version 11.0.8.

References

Community reviews

Loading reviews…