CVE-2026-37539
Buffer Overflow in Cannelloni CAN Frame Parsing
Publication date: 2026-05-01
Last updated on: 2026-05-05
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-121 | A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
The impact of this vulnerability includes the possibility of a denial of service, where the Cannelloni application crashes and stops functioning. More severely, it may allow remote attackers to execute arbitrary code, which could lead to full system compromise, unauthorized access, or control over the affected machine running Cannelloni.
Can you explain this vulnerability to me?
This vulnerability is a buffer overflow in the Cannelloni software version 2.0.0. It occurs in the CAN frame parsing functions parseCANFrame and decodeFrame when processing CAN FD frames. A remote attacker can exploit this by sending specially crafted CAN FD frames, which can cause the software to crash (denial of service) or potentially allow the attacker to execute arbitrary code on the affected system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability involves a buffer overflow in cannelloni v2.0.0 when parsing CAN FD frames. Detection would involve monitoring for abnormal crashes or denial of service symptoms in the cannelloni application when it processes CAN FD frames.
Since cannelloni is a SocketCAN over Ethernet tunnel, you can monitor the network traffic for crafted CAN FD frames that might trigger the vulnerability.
Specific commands are not provided in the available resources, but general approaches include:
- Using system logs and application logs to detect crashes or unusual behavior in cannelloni.
- Using network packet capture tools like tcpdump or Wireshark to capture CAN FD frames on the network and analyze them for suspicious or malformed frames.
- Running cannelloni in a debug mode or with logging enabled to trace frame parsing issues.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps are not explicitly detailed in the provided resources.
However, general best practices include:
- Avoid using cannelloni v2.0.0 in production environments, especially with untrusted CAN FD traffic.
- Restrict network access to the cannelloni service to trusted hosts only.
- Monitor and filter CAN FD frames to prevent malformed or crafted frames from reaching the vulnerable parsing functions.
- Apply any available patches or updates from the cannelloni project once released.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.