# CVE-2026-80217: Command injection in FF-RFI078I4

> An authenticated user with SSH access can execute arbitrary OS commands on LITE-ON RFID readers due to hidden functionality.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-g28v-9m8c-rvf6

## What is CVE-2026-80217?

CVE-2026-80217 is a high-severity command injection vulnerability in LITE-ON Technology Corporation FF-RFI078I4, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Hidden functionality issue exists in FF-RFI079I4 and FF-RFI078I4, which may allow a user who can log in via SSH and access the enable mode on the product to execute arbitrary OS commands.

Weakness: CWE-912 (Hidden Functionality)

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


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

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

## Is CVE-2026-80217 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80217 is a high-severity command injection vulnerability in LITE-ON Technology Corporation FF-RFI078I4, published on 15 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-80217 in the wild and no public exploit code.

Affected product: LITE-ON Technology Corporation FF-RFI078I4. 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-80217/ (Markdown: https://insights.sbomify.com/CVE-2026-80217/index.md)
```

## Sources

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

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