# CVE-2026-40852: Command injection via malicious configuration

> Authenticated attackers can inject commands into configuration generators, leading to remote code execution on industrial controllers.

- **Severity:** High 7.2 (`CVSS:3.1/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:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-4334-w3q6-m8g5

## What is CVE-2026-40852?

CVE-2026-40852 is a high-severity command injection vulnerability in Helmholz REX100, published on 27 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A highly authenticated attacker can alter the config generator injecting a payload into future created configurations. The device is not correctly checking this configuration value before passing it to an system execute leading to code execution. This can result in a total loss of confidentiality, integrity and availability.

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

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


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

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

## Is CVE-2026-40852 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40852 is a high-severity command injection vulnerability in Helmholz REX100, published on 27 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-40852 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-40852/ (Markdown: https://insights.sbomify.com/CVE-2026-40852/index.md)
```

## Sources

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

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