# CVE-2026-53629: GLPI: SQL injection in history tab

> An attacker with log read access can inject SQL via the history tab URL, allowing unauthorized database access in GLPI.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:L/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:** 25 Sep 2026
- **Also known as:** GHSA-cpcj-x335-5cmh, UBUNTU-CVE-2026-53629

## What is CVE-2026-53629?

CVE-2026-53629 is a high-severity SQL injection 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 9.4.0 until 10.0.26 and 11.0.8, an attacker with the READ right on logs can craft a URL for the history tab that injects attacker-controlled values into a database query. This permits SQL injection through the history tab endpoint. This issue is fixed in versions 11.0.8 and 10.0.26.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-53629 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53629 exists.

Public exploit code:

- PoC for CVE-2026-53629, blind SQL injection in the GLPI history log filter (github_poc): https://github.com/5kr1pt/glpi-logbleed
- GLPI - Blind SQL Injection in History Log Filter (LogBleed) (nuclei): http/cves/2026/CVE-2026-53629.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53629 is a high-severity SQL injection 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53629 exists.

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-53629/ (Markdown: https://insights.sbomify.com/CVE-2026-53629/index.md)
```

## Sources

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

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