# CVE-2026-9166: LFI in GIS Informatics' GisLab Laboratory Management System

> An attacker can exploit a path traversal vulnerability to read arbitrary files from the server in the GisLab Laboratory Management System.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-h35h-27m7-j6fc

## What is CVE-2026-9166?

CVE-2026-9166 is a high-severity path traversal vulnerability in GisLab Laboratory Management System, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in GIS Informatics GisLab Laboratory Management System allows Path Traversal.

This issue affects GisLab Laboratory Management System: from 1.4.03 before 1.5.

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

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


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

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

## Is CVE-2026-9166 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9166 is a high-severity path traversal vulnerability in GisLab Laboratory Management System, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9166 in the wild and no public exploit code.

Affected product: GisLab Laboratory Management System. 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-9166/ (Markdown: https://insights.sbomify.com/CVE-2026-9166/index.md)
```

## Sources

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

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