# CVE-2025-26856: Command injection in UD-LT2

> An authenticated administrator can execute arbitrary OS commands on I-O DATA UD-LT2 devices by manipulating specific screen requests.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2025
- **Updated:** 20 Feb 2025
- **Also known as:** GHSA-p9q9-h36m-37f9

## What is CVE-2025-26856?

CVE-2025-26856 is a high-severity command injection vulnerability in I-O DATA DEVICE, INC. UD-LT2, published on 20 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper neutralization of special elements used in an OS command ('OS Command Injection') issue exists in UD-LT2 firmware Ver.1.00.008_SE and earlier. If an attacker logs in to the affected product with an administrative account and manipulates requests for a certain screen operation, an arbitrary OS command may be executed. This vulnerability was reported on a different screen operation from CVE-2025-20617.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-26856?


## How do I fix CVE-2025-26856?

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

## Is CVE-2025-26856 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-26856 and fix it if it is affected.

What it is: CVE-2025-26856 is a high-severity command injection vulnerability in I-O DATA DEVICE, INC. UD-LT2, published on 20 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-26856 in the wild and no public exploit code.

Affected product: I-O DATA DEVICE, INC. UD-LT2. 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-2025-26856/ (Markdown: https://insights.sbomify.com/CVE-2025-26856/index.md)
```

## Sources

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

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