# CVE-2026-40851: Command injection via USB

> A local attacker can execute arbitrary code via a crafted USB file, compromising industrial controllers.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-hcr2-wfhw-2h9m

## What is CVE-2026-40851?

CVE-2026-40851 is a high-severity command injection vulnerability in Helmholz REX100, published on 27 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A local attacker can perform a confusion attack on the cfgparser via a specially crafted file on an USB stick leading to code execution. This can result in a total loss of confidentiality, integrity and availability.

Weakness: CWE-1287 (Improper Validation of Specified Type of Input)

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


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

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

## Is CVE-2026-40851 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40851 is a high-severity command injection vulnerability in Helmholz REX100, published on 27 May 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-40851 in the wild and no public exploit code.

Affected product: Helmholz REX100. 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-40851/ (Markdown: https://insights.sbomify.com/CVE-2026-40851/index.md)
```

## Sources

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

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