System crash via unchecked CANswitch length
Published May 1, 2026 · Updated May 1, 2026
Stack-based buffer overflow in OVMS3 3.3.005 allows remote attackers to crash the module via crafted CANswitch frames. The CANswitch log parser uses a header-supplied length to drive memcpy into a fixed-size stack buffer without an upper-bound check. The upstream project states that the report lacks technical analysis and remains under investigation, so remote reachability and code execution are unverified.
Summary
What happened
Stack-based buffer overflow in OVMS3 3.3.005 allows remote attackers to crash the module via crafted CANswitch frames. The CANswitch log parser uses a header-supplied length to drive memcpy into a fixed-size stack buffer without an upper-bound check. The upstream project states that the report lacks technical analysis and remains under investigation, so remote reachability and code execution are unverified.
The record
- CVE
- CVE-2026-42469
- Published
- May 1, 2026
- Updated
- May 1, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-121
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 1, 2026CVE publishedPublication date reported by the CVE source.
- May 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo