# CVE-2026-48482: GLPI: RCE via Form import

> A form administrator can exploit path traversal in GLPI to write malicious scripts to executable locations, enabling remote code execution.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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-6whc-g4h2-98rm, UBUNTU-CVE-2026-48482

## What is CVE-2026-48482?

CVE-2026-48482 is a critical path traversal 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 11.0.0 until 11.0.8, a form administrator can use Form import with a crafted illustration or scene identifier that traverses outside the intended custom-asset directory. The imported file can be written to an executable server location, allowing a malicious script to be invoked remotely. This issue is fixed in version 11.0.8.

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

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


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

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

## Is CVE-2026-48482 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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