# CVE-2026-53627: GLPI: Unexpected access to update operations through the API


- **Severity:** Medium 6.0 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-p68f-rv24-mc54, UBUNTU-CVE-2026-53627

## What is CVE-2026-53627?

CVE-2026-53627 is a medium-severity vulnerability in glpi-project glpi, published on 25 Sep 2026. 

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-53627?


## How do I fix CVE-2026-53627?

No fix has been published for CVE-2026-53627 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-53627 being exploited?

There is no known exploitation of CVE-2026-53627 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53627 and fix it if it is affected.

What it is: CVE-2026-53627 is a medium-severity vulnerability in glpi-project glpi, published on 25 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-53627 in the wild and no public exploit code.

Affected product: glpi-project glpi. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53627/ (Markdown: https://insights.sbomify.com/CVE-2026-53627/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53627
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53627
- OSV: https://osv.dev/vulnerability/CVE-2026-53627

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53627/
Summaries are generated and may contain mistakes; the official description above is the record.