# CVE-2026-71453: Path traversal in EasyIO FS32

> An attacker can exploit a path traversal vulnerability in Johnson Controls EasyIO FS32 to read or modify arbitrary files on the device.

- **Severity:** Medium 5.6 (`CVSS:4.0/AV:A/AC:H/AT:P/PR:H/UI:N/VC:L/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-fpw9-622h-f9qj

## What is CVE-2026-71453?

CVE-2026-71453 is a medium-severity path traversal vulnerability in Johnson Controls EasyIO FS32, published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

- External Control of File Name or Path vulnerability in Johnson Controls EasyIO FS32 allows - traversal attack.

This issue affects EasyIO FS32: before 3.0b63.

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

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


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

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

## Is CVE-2026-71453 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71453 is a medium-severity path traversal vulnerability in Johnson Controls EasyIO FS32, published on 1 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-71453 in the wild and no public exploit code.

Affected product: Johnson Controls EasyIO FS32. 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-71453/ (Markdown: https://insights.sbomify.com/CVE-2026-71453/index.md)
```

## Sources

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

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