Malicious firmware upload via unauthenticated Bluetooth pairing
Published Apr 21, 2026 · Updated Apr 21, 2026
Key exchange without entity authentication in Zero Motorcycles Firmware 44 and earlier allows physically proximate attackers to pair over Bluetooth. The Bluetooth pairing flow accepts a device key exchange without authenticating the device identity, then exposes over-the-air firmware update functions. Exploitation requires pairing mode, knowledge of the full pairing process, and sustained proximity throughout the update, enabling malicious firmware upload.
Summary
What happened
Key exchange without entity authentication in Zero Motorcycles Firmware 44 and earlier allows physically proximate attackers to pair over Bluetooth. The Bluetooth pairing flow accepts a device key exchange without authenticating the device identity, then exposes over-the-air firmware update functions. Exploitation requires pairing mode, knowledge of the full pairing process, and sustained proximity throughout the update, enabling malicious firmware upload.
The record
- CVE
- CVE-2026-1354
- Published
- Apr 21, 2026
- Updated
- Apr 21, 2026
- Vendor
- Zero Motorcycles
- Product
- Zero Motorcycles Firmware
- Classifications
- CWE-322
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2026CVE publishedPublication date reported by the CVE source.
- Apr 21, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=44
What conditions does exploitation require?
What is affected?
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