# CVE-2026-29988: Information disclosure in AM102/102L V2

> An attacker with physical proximity can read NFC tags to extract LoRaWAN keys, enabling traffic decryption and command forgery on Milesight IoT devices.

- **Severity:** High 8.3 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:H/SA:N`)
- **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:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-x7rj-767c-4728

## What is CVE-2026-29988?

CVE-2026-29988 is a high-severity vulnerability in Milesight AM102/102L V2, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A cleartext transmission of sensitive information vulnerability in the NFC interface of multiple Milesight IoT device models running affected firmware versions allows an unauthenticated attacker with physical proximity to retrieve LoRaWAN ABP NwkSKey and AppSKey values and D2D keys via an NFC read operation. The exposed keys can be used to decrypt LoRaWAN traffic, forge uplink and downlink frames, submit falsified sensor data, issue supported device commands, and cause subsequent legitimate frames to be rejected.

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

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


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

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

## Is CVE-2026-29988 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-29988 is a high-severity vulnerability in Milesight AM102/102L V2, published on 26 Aug 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-29988 in the wild and no public exploit code.

Affected product: Milesight AM102/102L V2. 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-29988/ (Markdown: https://insights.sbomify.com/CVE-2026-29988/index.md)
```

## Sources

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

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