PLC runtime crash via missing enipThread return
Published Oct 1, 2025 · Updated Oct 2, 2025
DoS in enipThread in OpenPLC Runtime version 3 before pull request #292 allows local users to crash the PLC runtime. The thread function falls through without returning a pointer, so compiler-generated execution reaches an illegal ud2 instruction when its server loop ends. Local access is required under the current configuration; the process crash halts automation and control logic managed by the runtime.
Summary
What happened
DoS in enipThread in OpenPLC Runtime version 3 before pull request #292 allows local users to crash the PLC runtime. The thread function falls through without returning a pointer, so compiler-generated execution reaches an illegal ud2 instruction when its server loop ends. Local access is required under the current configuration; the process crash halts automation and control logic managed by the runtime.
The record
- CVE
- CVE-2025-54811
- Published
- Oct 1, 2025
- Updated
- Oct 2, 2025
- Vendor
- OpenPLC Project
- Product
- OpenPLC Runtime version 3
- Classifications
- CWE-758, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 1, 2025CVE publishedPublication date reported by the CVE source.
- Oct 2, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <pull request #292
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo