# CVE-2026-49470: GLPI: Missing Rate Limiting on Login and TOTP Verification — Account Takeover via Brute Force

> Attackers can brute-force TOTP codes due to missing rate limiting, leading to account takeover in GLPI IT management software.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-mcv8-4hfg-5x2x, UBUNTU-CVE-2026-49470

## What is CVE-2026-49470?

CVE-2026-49470 is a high-severity vulnerability in glpi-project glpi, published on 25 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

GLPI is a free asset and IT management software package. From 11.0.0 until 11.0.8, the time-based one-time password verification endpoint does not limit failed submissions per user. An attacker who has obtained a user's primary authentication credentials can repeatedly submit TOTP values against the MFA verification flow, making brute-force compromise of the second factor and subsequent account takeover possible. This issue is fixed in version 11.0.8.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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


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

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

## Is CVE-2026-49470 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-49470 is a high-severity vulnerability in glpi-project glpi, published on 25 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49470 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-49470/ (Markdown: https://insights.sbomify.com/CVE-2026-49470/index.md)
```

## Sources

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

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