CVE-2025-15627: Hardcoded Cryptographic Keys in TP-Link Omada Adoption Protocol Authentication
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.67% (FIRST EPSS); higher than 52.6% of all records.
- Someone on the same network segment can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 3, 2026
- Updated
- Sep 29, 2026
- EPSS
- 0.6% · 52th percentile
- CWE
- CWE-321
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · TPLink
- 6.9
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| tp-link | omada ds1024g | cpe:2.3:h:tp-link:omada_ds1024g |
| tp-link | omada sx6632yf | cpe:2.3:h:tp-link:omada_sx6632yf |
| tp-link | omada oc200 v3 firmware | cpe:2.3:o:tp-link:omada_oc200_v3_firmware |
| tp-link | omada oc200 v3 | cpe:2.3:h:tp-link:omada_oc200_v3 |
| tp-link | omada oc300 firmware | cpe:2.3:o:tp-link:omada_oc300_firmware |
| tp-link | omada oc300 | cpe:2.3:h:tp-link:omada_oc300 |
| tp-link | omada oc400 firmware | cpe:2.3:o:tp-link:omada_oc400_firmware |
| tp-link | omada oc400 | cpe:2.3:h:tp-link:omada_oc400 |
| tp-link | omada fusion 2.5g firmware | cpe:2.3:o:tp-link:omada_fusion_2.5g_firmware |
| tp-link | omada fusion 2.5g | cpe:2.3:h:tp-link:omada_fusion_2.5g |
| tp-link | omada er707-m2 firmware | cpe:2.3:o:tp-link:omada_er707-m2_firmware |
| tp-link | omada er707-m2 | cpe:2.3:h:tp-link:omada_er707-m2 |
and 188 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (TPLink). Independent of NVD's CPE analysis and usually ahead of it.
TP Link Systems Inc. Omada Access Points
- 0affected
TP-Link Systems Inc Omada Controllers
- 0affected
TP-Link Systems Inc. Omada Gateways
- 0affected
TP-Link Systems Inc. Omada Switches
- 0affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- tp-link omada ds1008x firmwareall versions
- tp-link omada ds1016g firmwareall versions
- tp-link omada ds1016ge firmwareall versions
- tp-link omada ds1018gmp firmwareall versions
- tp-link omada ds1024g firmwareall versions
- tp-link omada ds105g firmwareall versions
- tp-link omada ds105g-m2 firmwareall versions
- tp-link omada ds105ge firmwareall versions
- tp-link omada ds105gp firmwareall versions
- tp-link omada ds105x firmwareall versions
- tp-link omada ds106gpp firmwareall versions
- tp-link omada ds106p firmwareall versions
- tp-link omada ds108g firmwareall versions
- tp-link omada ds108g-m2 firmwareall versions
- tp-link omada ds108ge firmwareall versions
- tp-link omada ds108gp firmwareall versions
- tp-link omada ds110gmp firmwareall versions
- tp-link omada ds111p firmwareall versions
- tp-link omada eap610 firmwareall versions
- tp-link omada eap610-outdoor firmwareall versions
Same product
tp-link: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-15628Hardcoded Certificates in TP-Link Omada Device Communications32Monitor
- CVE-2025-15629Weak Session Key Generation in TP-Link Omada Adoption Protocol27Monitor
- CVE-2025-15544Weak Credential Protection During TP-Link Omada Device Adoption27Monitor
Published before and after this one in the same product
- Later →CVE-2025-15630Aug 3, 2026 · Device Provisioning Race Condition in TP-Link Omada Adoption Workflow23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Stanislav Dashevskyi and Francesco La SpinaForescoutfinder
Not on record for this CVE: patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-321 · Use of Hard-coded Cryptographic KeyCVSS vector
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-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.