Project Subscriptions
No data.
No advisories yet.
Solution
* Enforce strict anti-replay: The receiver must maintain a persistent state (e.g., the counter value of the last valid code). It must never accept a code with a counter value less than or equal to the last known valid counter. * Secure resynchronization logic: The logic triggered by an old code is the flaw and must be removed. Secure resynchronization should only be triggered by codes that are ahead of the current counter to allow a "drifted" key fob to re-sync.
Workaround
No workaround given by the vendor.
| Link | Providers |
|---|---|
| https://asrg.io/security-advisories/cve-2026-2540/ |
|
Sun, 15 Feb 2026 11:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Micca KE700 system contains flawed resynchronization logic and is vulnerable to replay attacks. This attack requires sending two previously captured codes in a specific sequence. As a result, the system can be forced to accept previously used (stale) rolling codes and execute a command. Successful exploitation allows an attacker to clone the alarm key. This grants the attacker unauthorized access to the vehicle to unlock or lock the doors. | |
| Title | Micca KE700 Acceptance of previously used rolling codes | |
| Weaknesses | CWE-288 CWE-294 |
|
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: ASRG
Published:
Updated: 2026-02-15T11:03:26.051Z
Reserved: 2026-02-15T10:49:22.820Z
Link: CVE-2026-2540
No data.
Status : Received
Published: 2026-02-15T11:15:55.070
Modified: 2026-02-15T11:15:55.070
Link: CVE-2026-2540
No data.
OpenCVE Enrichment
No data.