Is CVE-2026-53627 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-53627 being exploited in the wild.

How severe is CVE-2026-53627?

Informational severity, published 25 September 2026.

Which products and versions are affected?

GLPI Project GLPI 11.0.0 to 11.0.7.

Is there a fix for CVE-2026-53627?

A patch was published on 2026-06-24: Fixed in version 11.0.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-53627 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-53627?

Check whether you run GLPI Project GLPI at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53627: GLPI authorization bypass in API update operations

CVE-2026-53627 · Severity: info · Published 2026-09-25

GLPI is a free asset and IT management software used to track hardware, software, and IT operations. A low-privileged authenticated user can bypass authorization controls through the API to perform updates that their user account normally cannot do through the web interface, potentially allowing unauthorized changes to managed assets and system configuration.

Technologies: GLPI Project GLPI. Vendors: GLPI Project.

Quick answers

Is CVE-2026-53627 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53627 being exploited in the wild.
How severe is CVE-2026-53627?: Informational severity, published 25 September 2026.
Which products and versions are affected?: GLPI Project GLPI 11.0.0 to 11.0.7.
Is there a fix for CVE-2026-53627?: A patch was published on 2026-06-24: Fixed in version 11.0.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53627 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-53627?: Check whether you run GLPI Project GLPI at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The GLPI API v2 update flow fails to consistently enforce authorization checks that are properly enforced in the user interface, allowing low-privileged authenticated users to perform unauthorized update operations. The vulnerability affects versions 11.0.0 through 11.0.7 and was patched in 11.0.8 by adding Session::haveRight authorization checks to API endpoints like transferEntity. An authenticated attacker with low privileges can exploit this to modify data they should not have access to.

Affected products

GLPI Project GLPI 11.0.0 to 11.0.7

Timeline

2026-09-25: disclosed
2026-06-24: patched: Fixed in version 11.0.8

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.