# CVE-2026-79625: Improper Synchronization in Monitoring in CODESYS Control Runtime

> An authenticated remote attacker can exploit a race condition in monitoring to cause denial of service or data corruption in CODESYS Control Runtime.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/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:** 30 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-crvr-hhmx-9hp6

## What is CVE-2026-79625?

CVE-2026-79625 is a high-severity vulnerability in CODESYS Control RTE (SL), published on 30 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Affected products do not properly synchronize access to their monitoring functionality. When multiple clients send concurrent requests, this may lead to incorrect reads or writes, or to corruption of internal memory structures. An authenticated remote attacker with monitoring access can exploit this issue to cause incorrect data processing or a denial-of-service condition.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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


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

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

## Is CVE-2026-79625 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79625 is a high-severity vulnerability in CODESYS Control RTE (SL), published on 30 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-79625 in the wild and no public exploit code.

Affected product: CODESYS Control RTE (SL). 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-79625/ (Markdown: https://insights.sbomify.com/CVE-2026-79625/index.md)
```

## Sources

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

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