CVE-2025-15629
What it is
A cryptographic weakness exists in the Omada adoption protocol where session encryption keys used to protect communications between controllers and managed devices may be predictable due to insufficient entropy in session key generation. An attacker who successfully intercepts adoption-related communications may be able to recover session encryption keys and decrypt affected communications.
At a glance
- Exploitability
- Can be exploited from the same network segment without logging in, but needs a user to act. High risk of data exposure.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 6.9 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-331
- Record status
- Analyzed
Affected
- TP-Link Omada oc200 v3 Firmware
- TP-Link Omada oc300 Firmware
- TP-Link Omada oc400 Firmware
- TP-Link Omada Fusion 2.5g Firmware
- TP-Link Omada er707-m2 Firmware
- TP-Link Omada er7206 Firmware
- TP-Link Omada er706w Firmware
- TP-Link Omada er8411 Firmware
Attack profile CVSS 4.0 · 6.9
- Attack vector
- Adjacent network
- Complexity
- Low
- Attack requirements
- Present
- Privileges needed
- None
- User interaction
- Passive
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Raw 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
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-15629.md and follow it. Check whether this project is affected by CVE-2025-15629. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
