CVE-2026-37554
Deferred Deferred - Pending Action
Denial of Service in Vanetza V2X

Publication date: 2026-05-01

Last updated on: 2026-05-05

Assigner: MITRE

Description
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 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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-01
Last Modified
2026-05-05
Generated
2026-05-07
AI Q&A
2026-05-01
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
vanetza v2x 26.02
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-248 An exception is thrown from a function, but it is not caught.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in Vanetza V2X version 26.02 and allows remote unauthorized attackers to cause a denial of service (DoS). It occurs in the GeoNetworking packet processing pipeline where OpenSSL exceptions related to ECC point validation (such as invalid compressed points or points not on the curve) are not properly handled. Specifically, the OpenSSL wrapper's check() function throws exceptions when these validation errors occur, but these exceptions are not caught correctly in the Router::indicate() call chain. As a result, the exception escapes through later processing stages, leading to a std::terminate call that crashes the V2X receiver.


How can this vulnerability impact me? :

The primary impact of this vulnerability is a denial of service condition on the Vanetza V2X receiver. An attacker can remotely trigger this by sending malformed packets that cause OpenSSL ECC validation failures, which in turn crash the receiver software. This disruption could prevent the affected system from processing V2X communications, potentially impacting vehicle-to-everything communication reliability and safety functions.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability in Vanetza V2X v26.02 causes a denial of service by crashing the V2X receiver, leading to loss of cooperative awareness in vehicular communication systems.

While the CVE description and resources detail the technical impact and potential disruption to vehicular communication services, there is no direct information provided about how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by monitoring for crashes or unexpected terminations of the Vanetza V2X receiver, which occur due to unhandled OpenSSL exceptions in the GeoNetworking packet processing pipeline.

Detection can also involve capturing and analyzing malformed ETSI ITS payloads such as CAM, DENM, or GeoNetworking headers that cause out-of-bounds reads or NULL pointer dereferences.

Network monitoring tools can be used to capture 802.11p frames or V2X packets and inspect them for malformed or suspicious packets that might trigger the vulnerability.

While no specific commands are provided in the resources, general approaches include using packet capture tools like tcpdump or Wireshark to filter and analyze V2X traffic, for example:

  • tcpdump -i <interface> -w capture.pcap 'ether proto 0x88dc' # Capture GeoNetworking packets
  • wireshark capture.pcap # Analyze captured packets for malformed headers or payloads

Additionally, monitoring the Vanetza application logs for crashes or std::terminate calls related to OpenSSL exceptions can help detect exploitation attempts.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include restricting network access to the Vanetza V2X nodes to trusted sources only, minimizing exposure to untrusted or potentially malicious V2X traffic.

Implement network-level filtering to block malformed or suspicious ETSI ITS payloads such as CAM, DENM, or GeoNetworking packets that could trigger the vulnerability.

Monitor the Vanetza V2X system for crashes and restart the service promptly if a crash occurs to maintain availability.

Apply any available patches or updates from the Vanetza project that address this vulnerability once they are released.

Consider deploying intrusion detection or prevention systems capable of recognizing malformed V2X packets to prevent exploitation.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart