# CVE-2025-54811: OpenPLC_V3

> Remote unauthenticated attackers can crash the OpenPLC runtime by triggering a specific server loop condition, halting automation logic.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA: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:** 1 Oct 2025
- **Updated:** 2 Oct 2025
- **Also known as:** GHSA-v57j-j5hj-cgf3

## What is CVE-2025-54811?

CVE-2025-54811 is a medium-severity denial of service vulnerability in OpenPLC_V3, published on 1 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenPLC_V3 has a vulnerability in the enipThread function that occurs due to the lack of a return value. This leads to a crash when the server loop ends and execution hits an illegal ud2 instruction. This issue can be triggered remotely without authentication by starting the same server multiple times or if the server exits unexpectedly. The vulnerability allows an attacker to cause a Denial of Service (DoS) against the PLC runtime, stopping any PC started remotely without authentication. This results in the PLC process crashing and halting all automation or control logic managed by OpenPLC.

Weakness: CWE-758 (Reliance on Undefined, Unspecified, or Implementation-Defined Behavior)

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


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

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

## Is CVE-2025-54811 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54811 is a medium-severity denial of service vulnerability in OpenPLC_V3, published on 1 Oct 2025. 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-2025-54811 in the wild and no public exploit code.

Affected product: OpenPLC_V3. 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-54811/ (Markdown: https://insights.sbomify.com/CVE-2025-54811/index.md)
```

## Sources

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

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