VulnerabilityPublished 21 Nov 2024Updated 3 Dec 2024

CVE-2024-53429: open62541 · Reachable Assertion

Affects open62541Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubopen62541/open62541`pkg:github/open62541/open62541`Other threats	Affected =1.4.6	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Monitor the Open62541 project for official patches addressing CVE-2024-53429 and apply them promptly once released.
Until patches are available, implement network-level protections such as firewall rules or intrusion prevention systems to restrict access to OPC UA servers running Open62541, limiting exposure to trusted sources only.
Employ application-layer gateways or OPC UA proxies that can validate and sanitize incoming binary data to prevent malformed inputs from reaching vulnerable components.
Conduct thorough input validation and fuzz testing in development environments to identify and mitigate similar vulnerabilities proactively.
Implement robust monitoring and alerting for OPC UA server crashes or unusual behavior to enable rapid incident response.
Consider segmenting industrial networks to isolate OPC UA servers from less trusted network segments, reducing the attack surface.
Educate operational technology (OT) and security teams about this vulnerability to ensure coordinated response and mitigation efforts.

Description

Open62541 v1.4.6 is has an assertion failure in fuzz_binary_decode, which leads to a crash.

Impact

The primary impact of CVE-2024-53429 is denial of service against systems running Open62541 v1.4.6, which can disrupt industrial automation and control processes that rely on OPC UA communication. This can lead to operational downtime, reduced productivity, and potential safety hazards in critical infrastructure sectors such as manufacturing, energy, utilities, and transportation. Since the vulnerability can be exploited remotely without authentication, attackers can cause widespread disruption with minimal effort. Although confidentiality and integrity are not directly affected, the loss of availability in industrial control systems can have cascading effects, including delayed responses to operational events and increased risk of physical damage. Organizations with large-scale OPC UA deployments or those integrating Open62541 into their control systems are at heightened risk. The absence of known exploits in the wild provides a window for proactive mitigation, but the potential impact on critical infrastructure makes this vulnerability a serious concern.

CWE-617Reachable Assertion (opens in a new tab)
Base weakness
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
Implementation
Make sensitive open/close operation non reachable by directly user-controlled data (e.g. open/close resources)
Implementation · Input Validation
Perform input validation on user data.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/open62541/open62541/issues/6825 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 01:42 UTC

WeaknessesCWE-617

Technical details

References

Community reviews

Related threats