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.
CVE-2026-29988
Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-08-26. a secondary CVSS source baseline 7.6; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.6
- EG Score
- 7.6(high)
- EG Risk
- 34(Track)EG Risk 34/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity76% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 5%
- KEV
- Not listed
Published
August 26, 2026
Last Modified
August 26, 2026
Advisory Details (1)
Auto-updated Aug 26, 2026Vulnerabilities in Some Milesight Sensors | Milesight
https://www.milesight.com/legal/vulnerabilities-in-some-milesight-sensorsVendor Advisories for CVE-2026-29988(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× 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-08-27 18:23 UTCEG score recompute
- 2026-08-27 18:23 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 05:22 UTCEG score recompute
- 2026-08-27 05:22 UTCGHSA enrichment
- 2026-08-26 16:22 UTCEG score recompute
- 2026-08-26 15:56 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 03:20 UTCEG score recompute
- 2026-08-26 03:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-319
Frequently asked(5)
What is CVE-2026-29988?
When was CVE-2026-29988 disclosed?
Is CVE-2026-29988 actively exploited?
What is the CVSS score of CVE-2026-29988?
How do I remediate CVE-2026-29988?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-29988
Is Your Infrastructure Affected by CVE-2026-29988?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.