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.
This CVE has been withdrawn by MITRE
MITRE marked CVE-2026-80216 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
Reason given by MITRE
duplicate record
CVE-2026-80216
✕ Withdrawn — historical dataHIGHPre-NVD 7.6
7.6CVSS
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.6Exploit: None knownExposed services: Not assessed
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 7.6
- EchelonGraph score
- Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
- EG Score
- —
- EG Risk
- —
- EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 26, 2026
Last Modified
August 26, 2026
Advisory Details (1)
Auto-updated Aug 26, 2026No patch confirmed yet.
generic
Vulnerabilities in Some Milesight Sensors | Milesight
https://www.milesight.com/legal/vulnerabilities-in-some-milesight-sensorsWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 1× in last 7d / 1× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-30 20:01 UTCEG score recompute
- 2026-08-27 04:16 UTCEG score recompute▼ 7.60
- 2026-08-26 02:55 UTCEG score recompute
- 2026-08-26 02:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-80216?
CVE-2026-80216 is a high vulnerability published on August 26, 2026. 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…
When was CVE-2026-80216 disclosed?
CVE-2026-80216 was first published on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-80216?
CVE-2026-80216 has a CVSS base score of 7.6 (the CNA's own assessment, by mitre; NVD's own analysis pending).
How do I remediate CVE-2026-80216?
No fix for CVE-2026-80216 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-80216
Is Your Infrastructure Affected by CVE-2026-80216?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.