CVE-2025-15627 json
Hardcoded Cryptographic Keys in TP-Link Omada Adoption Protocol Authentication
published 2026-08-03 3 mo ago modified 2026-09-29 41 d ago also EUVD-2025-210609
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
A cryptographic weakness exists in the Omada adoption protocol. The protocol relies on hard-coded cryptographic keys to establish trust and protect authentication exchanges between controllers and managed devices during device adoption.
An attacker may be able to impersonate trusted controllers or managed devices and gain access to sensitive adoption-related communications.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N |
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- TP-Link Systems Inc. Omada Gateways
- TP-Link Systems Inc. Omada Switches
- TP Link Systems Inc. Omada Access Points
- TP-Link Systems Inc Omada Controllers
Classification
- Weakness
-
- CWE-321 Use of Hard-coded Cryptographic Key
References
-
omadanetworks.com
/us/support/download/
patch, product
-
omadanetworks.com
/en/support/download/
patch, product
-
tp-link.com
/us/support/faq/5216/
vendor-advisory
Sources
- CVE List CVE-2025-15627
- NVD CVE-2025-15627
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.