# CVE-2026-82765: Path traversal in FXA3000

> Attackers with FTP access can view or alter arbitrary files on Contec FX series industrial devices due to a path traversal vulnerability.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-3vqr-mgc9-pjp4

## What is CVE-2026-82765?

CVE-2026-82765 is a high-severity path traversal vulnerability in Contec Co., Ltd. FXA3000, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Path traversal vulnerability exists in Contec FX5000 series, FX4000 series, and FX3000 series. If this vulnerability is exploited, arbitrary files on the server may be viewed and/or altered by an attacker who can access the product via FTP.

Weakness: CWE-23 (Relative Path Traversal)

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


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

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

## Is CVE-2026-82765 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82765 is a high-severity path traversal vulnerability in Contec Co., Ltd. FXA3000, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82765 in the wild and no public exploit code.

Affected product: Contec Co., Ltd. FXA3000. 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-82765/ (Markdown: https://insights.sbomify.com/CVE-2026-82765/index.md)
```

## Sources

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

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