# CVE-2025-41739: CODESYS Control - Linux/QNX SysSocket flaw

> An unauthenticated remote attacker can cause a denial of service in CODESYS Control runtime systems by exploiting a race condition leading to an out-of-bounds read.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2025
- **Updated:** 7 Jan 2026
- **Also known as:** GHSA-5qp2-82v4-wwr8

## What is CVE-2025-41739?

CVE-2025-41739 is a medium-severity vulnerability in CODESYS Control for BeagleBone SL, published on 1 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated remote attacker, who beats a race condition, can exploit a flaw in the communication servers of the CODESYS Control runtime system on Linux and QNX to trigger an out-of-bounds read via crafted socket communication, potentially causing a denial of service.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2025-41739 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41739 is a medium-severity vulnerability in CODESYS Control for BeagleBone SL, published on 1 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41739 in the wild and no public exploit code.

Affected product: CODESYS Control for BeagleBone 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-2025-41739/ (Markdown: https://insights.sbomify.com/CVE-2025-41739/index.md)
```

## Sources

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

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