# CVE-2026-2539: Micca KE700 Cleartext transmission of key fob ID

> Attackers can intercept cleartext RF data to capture authentication credentials, potentially bypassing security in Micca KE700 car alarms.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:P/AU:N/V:D/RE:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2026
- **Updated:** 17 Feb 2026
- **Also known as:** GHSA-88gg-5jpf-jc8f

## What is CVE-2026-2539?

CVE-2026-2539 is a medium-severity vulnerability in Micca Auto Electronics Co., Ltd. Car Alarm System KE700, published on 15 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The RF communication protocol in the Micca KE700 car alarm system does not encrypt its data frames. An attacker with a radio interception tool (e.g., SDR) can capture the random number and counters transmitted in cleartext, which is sensitive information required for authentication.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2026-2539?


## How do I fix CVE-2026-2539?

No fix has been published for CVE-2026-2539 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2539 being exploited?

There is no known exploitation of CVE-2026-2539 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2539 and fix it if it is affected.

What it is: CVE-2026-2539 is a medium-severity vulnerability in Micca Auto Electronics Co., Ltd. Car Alarm System KE700, published on 15 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2539 in the wild and no public exploit code.

Affected product: Micca Auto Electronics Co., Ltd. Car Alarm System KE700. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2539/ (Markdown: https://insights.sbomify.com/CVE-2026-2539/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2539
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2539
- OSV: https://osv.dev/vulnerability/CVE-2026-2539

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2539/
Summaries are generated and may contain mistakes; the official description above is the record.