# CVE-2026-53628: GLPI: Unallowed authentication method update by administrator

> Administrators can bypass entity scope restrictions to change authentication methods and disable 2FA for users outside their assigned scope.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-2hf7-pw75-7wcp, UBUNTU-CVE-2026-53628

## What is CVE-2026-53628?

CVE-2026-53628 is a medium-severity missing authorization vulnerability in glpi-project glpi, published on 25 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

GLPI is a free asset and IT management software package. From 0.84 until 10.0.26 and 11.0.8, an administrator holding the Update auth and sync or Update auth, sync and 2FA right can change the authentication method and disable two-factor authentication for user accounts outside the administrator's entity scope. The affected user-account administration flow did not consistently enforce the target user's entity-scoped update permission. This issue is fixed in versions 11.0.8 and 10.0.26.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-53628 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53628 is a medium-severity missing authorization vulnerability in glpi-project glpi, published on 25 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53628 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-53628/ (Markdown: https://insights.sbomify.com/CVE-2026-53628/index.md)
```

## Sources

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

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