AM102/102L V2: Cleartext Transmission of Sensitive Information
CVE-2026-29988 is a high-severity cleartext transmission of sensitive information vulnerability in AM102/102L V2 from MileSight, with a CVSS 3.1 base score of 7.6 out of 10. It can be exploited with physical access to the device by an unauthenticated attacker, without any action from a user. Affected AM102/102L V2 versions: 1.4 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.17% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of AM102/102L V2 you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Milesight | AM102/102L V2 | 1.4 and earlier | Not stated |
| Milesight | AM103/103L V2 | 1.8 and earlier | Not stated |
| Milesight | AM304L | 1.2 and earlier | Not stated |
| Milesight | AM305L | 1.2 and earlier | Not stated |
| Milesight | AM307 V2 | 1.4 and earlier | Not stated |
| Milesight | AM308 | 1.7 and earlier | Not stated |
| Milesight | AM308L | 1.7 and earlier | Not stated |
| Milesight | AM319 | 1.6 and earlier | Not stated |
| Milesight | WS101 | 1.5 and earlier | Not stated |
| Milesight | WS136 | 1.6 and earlier | Not stated |
| Milesight | WS156 | 1.6 and earlier | Not stated |
| Milesight | WS201 | 1.2 and earlier | Not stated |
| Milesight | WS202 | 1.8 and earlier | Not stated |
| Milesight | WS203 | 1.3 and earlier | Not stated |
| Milesight | WS301 | 1.15 and earlier | Not stated |
| Milesight | WS303 | 1.5 and earlier | Not stated |
| Milesight | WS50X (2W-W11-EU) [501/502/503] | 1.3 and earlier | Not stated |
| Milesight | WS50X (3W-W11-EU) [501/502/503] | 1.2 and earlier | Not stated |
| Milesight | WS50X (3W-W12-EU) [501/502/503] | 1.2 and earlier | Not stated |
| Milesight | WS51X [513/515] | 1.9 and earlier | Not stated |
| Milesight | WS52X [523/525] | 1.12 and earlier | Not stated |
| Milesight | WS558 | 1.1 and earlier | Not stated |
| Milesight | VS321 | 321.1.0.1-r5 and earlier | Not stated |
| Milesight | VS360 | 1.2-r1 and earlier | Not stated |
| Milesight | VS350 V3 | 1.1 and earlier | Not stated |
Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- PhysicalThe attacker must physically touch the device.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (mitre.org).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.3 | High | CNA (mitre.org) |
| CVSS 3.1 | 7.6 | High | CNA (mitre.org) |
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Cleartext Transmission of Sensitive Information
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
How developers prevent this class of flaw
- Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
- When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
- When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
More Cleartext Transmission of Sensitive Information vulnerabilities (CWE-319)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Recent Cleartext Transmission of Sensitive Information vulnerabilities
- 7.7 High severity
- 7.4 High severity
- 10.0 Critical severity
- 9.1 Critical severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.