# CVE-2026-41116: Path traversal in Inventory Collector Client

> A local low-privileged attacker can exploit improper link resolution to perform arbitrary file writes in Dell Inventory Collector Client.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-768m-67qh-jmhr

## What is CVE-2026-41116?

CVE-2026-41116 is a medium-severity path traversal vulnerability in Dell Inventory Collector Client, published on 9 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Dell Inventory Collector Client, versions prior to 13.8.0, contain an Improper Link Resolution Before File Access ('Link Following') vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Arbitrary File Write.

Weakness: CWE-1386 (Insecure Operation on Windows Junction / Mount Point)

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


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

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

## Is CVE-2026-41116 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41116 is a medium-severity path traversal vulnerability in Dell Inventory Collector Client, published on 9 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41116 in the wild and no public exploit code.

Affected product: Dell Inventory Collector Client. 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-41116/ (Markdown: https://insights.sbomify.com/CVE-2026-41116/index.md)
```

## Sources

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

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