# CVE-2026-47679: GLPI: arbitrary file deletion

> Logged-in users can delete arbitrary server files via path traversal in profile picture updates, requiring an upgrade to patched versions.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H`)
- **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-x5r8-r6vj-79cw, UBUNTU-CVE-2026-47679

## What is CVE-2026-47679?

CVE-2026-47679 is a high-severity path traversal 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 10.0.0 until 10.0.26 and 11.0.8, any logged-in GLPI user can exploit insufficient path validation in the profile-picture update flow to request deletion of an attacker-selected file hosted by the server. This issue is fixed in versions 11.0.8 and 10.0.26.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-47679 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47679 is a high-severity path traversal 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-47679 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-47679/ (Markdown: https://insights.sbomify.com/CVE-2026-47679/index.md)
```

## Sources

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

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