CVE Intelligence
High Authentication

CVE-2026-2540 — Micca KE700 Acceptance of previously used rolling codes

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.

Published Feb 15, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: ASRG

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.22%
ahead of 12% of scored CVEs · Oct 14, 2026
Affects
Micca Auto Electronics Co., Ltd.
Car Alarm System KE700
CVSS base
8.4
High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Micca Auto Electronics Co., Ltd. Car Alarm System KE700).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Micca Auto Electronics Co., Ltd. Car Alarm System KE700 version KE700 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Adjacent
Attack complexity
Low
Attack requirements
None
Privileges required
None
User interaction
None
Scope
X
Confidentiality (vulnerable system)
Low
Integrity (vulnerable system)
High
Availability (vulnerable system)
None
Confidentiality (subsequent)
Low
Integrity (subsequent)
Low
Availability (subsequent)
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.4 CVSS 4.0 High — — cve@asrg.io via NIST National Vulnerability Database
8.4 CVSS 4.0 High — — ASRG via CVE Program (cve.org) e CISA ADP
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:L/SI:L/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:D/RE:M/U:X (score shown at the top: cve@asrg.io)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-288 · Authentication Bypass Using an Alternate Path or Channel

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.22%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.
authentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · micca auto electronics co., ltd./car alarm system ke700
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 8.4
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Deferred
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Feb 15, 2026 · ASRG

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

Elsewhere on this site

Micca Auto Electronics Co., Ltd.
every CVE for this vendor
Authentication
same class
CWE-288
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-2541 Micca KE700 Brute-force vulnerability due to low entropy Feb 15, 2026
  • CVE-2026-2539 Micca KE700 Cleartext transmission of key fob ID Feb 15, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-2540 is "Micca KE700 Acceptance of previously used rolling codes", rated High. It affects Car Alarm System KE700 (Micca Auto Electronics Co., Ltd.); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.4 describes technical severity. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.