How severe is CVE-2024-53429?

CVE-2024-53429 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2024-53429 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (49th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2024-53429?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2024-53429 have an EU (EUVD) identifier?

Yes. CVE-2024-53429 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-51965.

When was CVE-2024-53429 published?

CVE-2024-53429 was published on 2024-11-21 and last updated on 2026-06-17.

CVE-2024-53429

CVE-2024-53429 is a high-severity vulnerability with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-617.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 1% (49th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-51965
Weakness: CWE-617
Published: 2024-11-21
Last modified: 2026-06-17

Description

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

Frequently asked questions

What is CVE-2024-53429?: Open62541 v1.4.6 is has an assertion failure in fuzz_binary_decode, which leads to a crash.
How severe is CVE-2024-53429?: CVE-2024-53429 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2024-53429 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (49th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2024-53429?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-53429 have an EU (EUVD) identifier?: Yes. CVE-2024-53429 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-51965.
When was CVE-2024-53429 published?: CVE-2024-53429 was published on 2024-11-21 and last updated on 2026-06-17.

References

https://github.com/open62541/open62541/issues/6825

Other CWE-617 (Reachable Assertion) vulnerabilities

CVE-2020-3615 — Critical (CVSS 9.8): Valid deauth/disassoc frames is dropped in case if RMF is enabled and some rouge peer keep on sending rogue…
CVE-2019-9795 — Critical (CVSS 9.8): A vulnerability where type-confusion in the IonMonkey just-in-time (JIT) compiler could potentially be used by…
CVE-2026-31739 — High (CVSS 8.8): In the Linux kernel, the following vulnerability has been resolved: crypto: tegra - Add missing CRYPTO_ALG_ASYNC The…
CVE-2020-12417 — High (CVSS 8.8): Due to confusion about ValueTags on JavaScript Objects, an object may pass through the type barrier, resulting in…
CVE-2020-6623 — High (CVSS 8.8): stb stb_truetype.h through 1.22 has an assertion failure in stbtt__cff_get_index.
CVE-2020-6619 — High (CVSS 8.8): stb stb_truetype.h through 1.22 has an assertion failure in stbtt__buf_seek.

Browse all CWE-617 (Reachable Assertion) vulnerabilities →