# CVE-2026-71170: Path traversal in Application Store

> A local low-privileged attacker can exploit an uncontrolled path element vulnerability in Dell Application Store to achieve privilege escalation and arbitrary code execution.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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:** 19 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-gx85-4c58-7cg4

## What is CVE-2026-71170?

CVE-2026-71170 is a high-severity path traversal vulnerability in Dell Application Store, published on 19 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Dell Application Store, versions prior to 26.05.0.7, contains an Uncontrolled Path Element vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to an Elevation of Privilege and arbitrary code execution.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2026-71170 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71170 is a high-severity path traversal vulnerability in Dell Application Store, published on 19 Oct 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-71170 in the wild and no public exploit code.

Affected product: Dell Application Store. 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-71170/ (Markdown: https://insights.sbomify.com/CVE-2026-71170/index.md)
```

## Sources

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

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