Cyber Resilience

CVE-2025-54811

Published
01 October 2025
Modified
15 April 2026
CVSS Score v4 6.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0020 10th percentile
Risk Priority 31 floored blend · peak EPSS

Summary

CVE-2025-54811 is a medium-severity Reliance on Undefined, Unspecified, or Implementation-Defined Behavior (CWE-758) vulnerability in Cisa (inferred from references). Its CVSS base score is 6.1 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-758

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
T1687 Exploitation for Defense Impairment Defense Impairment
Adversaries may exploit vulnerabilities in security software, infrastructure, or defensive components to degrade, disable, or otherwise continue to impair their ability to prevent, detect, or respond to malicious activity.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-30624Shared CWE-758
CVE-2026-34549Shared CWE-758
CVE-2026-4705Shared CWE-758
CVE-2026-50185Shared CWE-758
CVE-2024-4774Shared CWE-758
CVE-2026-34537Shared CWE-758
CVE-2026-34547Shared CWE-758
CVE-2026-16441Shared CWE-758
CVE-2026-4718Shared CWE-758
CVE-2025-55160Shared CWE-758

Affected Assets

Cisa
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover reliance on undefined behavior through cross-platform or stress testing.

SA-15 Development Process, Standards, and Tools partial match

Mandating a documented development process and coding standards directly discourages dependence on unspecified behavior.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require use of only well-defined language and API behaviors during development.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prohibit use of undefined or implementation-defined behavior in code.

PR.PS-01 partial match
prevents

Consistent hardened configurations reduce the chance of relying on unspecified implementation details.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect some instances of undefined behavior but does not prevent the root weakness.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle requires defined, portable coding practices that reduce reliance on undefined behavior.

A.8.27 Secure system architecture and engineering principles partial match
degrades

Secure system architecture and engineering principles mandate use of well-specified interfaces and avoid undefined constructs.

A.8.28 Secure coding partial match
prevents

Secure coding explicitly prohibits constructs whose behavior is undefined, unspecified or implementation-defined.

References