Ignition-key cloning via globally reused secret
Published Nov 29, 2025 · Updated Aug 17, 2026
Hard-coded cryptographic keys in motogadget mo.lock RFID 20251125 allow physically proximate attackers to clone ignition keys. The NFC handler accepts a globally reused secret and validates a captured 7-byte key UID against an exhaustible 16-bit password space. Brief contactless access to a legitimate key and an NFC emulator are required; a clone authenticates like the original and can switch vehicle power.
Summary
What happened
Hard-coded cryptographic keys in motogadget mo.lock RFID 20251125 allow physically proximate attackers to clone ignition keys. The NFC handler accepts a globally reused secret and validates a captured 7-byte key UID against an exhaustible 16-bit password space. Brief contactless access to a legitimate key and an NFC emulator are required; a clone authenticates like the original and can switch vehicle power.
The record
- CVE
- CVE-2025-6666
- Published
- Nov 29, 2025
- Updated
- Aug 17, 2026
- Vendor
- motogadget
- Product
- mo.lock RFID
- Classifications
- CWE-321, CWE-320, T1600.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 29, 2025CVE publishedPublication date reported by the CVE source.
- Aug 17, 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=20251125
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
- Contactless ignition-key cloning technical demonstrationproof of concept · demonstrated
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