CVE-2026-37554
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-37554 is a high-severity Uncaught Exception (CWE-248) vulnerability. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 28th 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-8 (Security and Privacy Engineering Principles) and SC-24 (Fail in Known State) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-37554 is a denial-of-service vulnerability in Vanetza V2X version v26.02, affecting the GeoNetworking packet processing pipeline. The issue arises when OpenSSL exceptions from ECC point validation—such as invalid compressed points or points not on the curve—are not properly caught during processing. Specifically, the openssl_wrapper.cpp check() function at line 19 throws an openssl::Exception on OpenSSL failures, but the parser's catch block in parse_secured() fails to handle it, allowing the exception to propagate through indicate_common() and indicate_extended() in Router::indicate(), ultimately triggering std::terminate() and crashing the V2X receiver. This is classified under CWE-248 (Uncaught Exception) with a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
Remote unauthorized attackers can exploit this vulnerability over the network with low complexity and no privileges required. By sending specially crafted packets that trigger ECC point validation failures in OpenSSL, attackers cause unhandled exceptions to escape the processing chain, resulting in an application crash via std::terminate(). The impact is limited to high availability disruption, rendering the V2X receiver inoperable until restart.
References include a detailed gist from the discoverer at https://gist.github.com/sgInnora/45128ae15d52df7238680a8f2da8359f and the official Vanetza repository at https://github.com/riebl/vanetza, with the vulnerable code in https://github.com/riebl/vanetza/blob/master/vanetza/geonet/router.cpp and https://github.com/riebl/vanetza/blob/master/vanetza/security/openssl_wrapper.cpp. No specific patches or mitigation steps are detailed in the provided information, but practitioners should review the repository for updates and ensure exception handling covers OpenSSL operations in security parsing.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-26671
Vulnerability Data
An issue was discovered in Vanetza V2X v26.02 allowing remote unauthorized attackers to cause a denial of service. The vulnerability exists in the GeoNetworking packet processing pipeline where OpenSSL exceptions from ECC point validation (invalid compressed point, point not on…
more
curve) are not properly caught by the Router::indicate() call chain. The openssl_wrapper.cpp check() function (line 19) throws openssl::Exception when OpenSSL operations fail. The parser's catch block in parse_secured() should catch these, but the exception escapes through subsequent processing stages (indicate_common, indicate_extended). This causes std::terminate, crashing the V2X receiver.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Security engineering principles include robust exception management to keep the system in a defined state.
Fail-in-known-state reduces the impact when an uncaught exception occurs by preserving a safe condition.
Error handling requirements force structured catching and response to exceptions instead of allowing them to propagate uncaught.
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.
Secure SDLC practices explicitly require structured exception handling to prevent uncaught exceptions from reaching production.
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.
Security testing can detect uncaught exceptions before production deployment.
Secure development lifecycle includes exception-handling standards that reduce uncaught exceptions.
Application security requirements typically mandate robust error and exception handling.
Secure architecture principles call for centralized, comprehensive exception management.
Secure coding standards directly require catching and handling exceptions to prevent crashes or leaks.