# CVE-2026-49469: GLPI: LDAP filter injection in user import feature

> Authenticated users can inject LDAP filters to bypass security controls and access restricted directory objects in GLPI.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/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:** 29 Sep 2026
- **Also known as:** GHSA-3cgm-rj32-hfwf, UBUNTU-CVE-2026-49469

## What is CVE-2026-49469?

CVE-2026-49469 is a medium-severity 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.70 until 10.0.26 and 11.0.8, an authenticated hotliner or technician can submit crafted criteria through the user import feature to bypass the configured default LDAP filter. This allows access to LDAP objects that the default filter was intended to exclude. This issue is fixed in versions 11.0.8 and 10.0.26.

Weakness: CWE-90 (Improper Neutralization of Special Elements used in an LDAP Query)

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


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

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

## Is CVE-2026-49469 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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