# CVE-2026-82789: Code injection in CONPROSYS HMI System(CHS)

> Authenticated attackers can execute arbitrary code via eval injection in CONPROSYS HMI System, posing a risk to industrial control environments.

- **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:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-6c68-h54j-7c3w

## What is CVE-2026-82789?

CVE-2026-82789 is a high-severity code injection vulnerability in Contec CONPROSYS HMI System(CHS), published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An improper neutralization of directives in dynamically evaluated code ('Eval Injection') issue exists in CONPROSYS HMI System(CHS). If exploited, arbitrary code may be executed by an attacker who can log in to the product.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

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


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

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

## Is CVE-2026-82789 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82789 is a high-severity code injection vulnerability in Contec CONPROSYS HMI System(CHS), published on 14 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-82789 in the wild and no public exploit code.

Affected product: Contec CONPROSYS HMI System(CHS). 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-82789/ (Markdown: https://insights.sbomify.com/CVE-2026-82789/index.md)
```

## Sources

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

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