# CVE-2026-73171: Path traversal in EKI-1242EIMS

> Remote authenticated attackers can overwrite arbitrary files on Advantech EKI-1242EIMS devices via a crafted backup archive upload.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/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:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-gm35-6jgf-v5fw

## What is CVE-2026-73171?

CVE-2026-73171 is a high-severity path traversal vulnerability in Advantech EKI-1242EIMS, published on 16 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Nozomi Networks Labs identified a CWE-73: External Control of File Name or Path vulnerability in the backup-restore workflow of Advantech EKI-1242EIMS in firmware version V1.06.01 that allows a remote authenticated attacker to overwrite arbitrary files on the device filesystem by uploading a crafted backup archive through the web management interface.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-73171 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73171 is a high-severity path traversal vulnerability in Advantech EKI-1242EIMS, published on 16 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-73171 in the wild and no public exploit code.

Affected product: Advantech EKI-1242EIMS. 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-73171/ (Markdown: https://insights.sbomify.com/CVE-2026-73171/index.md)
```

## Sources

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

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