Is CVE-2025-15629 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-15629 being exploited in the wild.

How severe is CVE-2025-15629?

High severity, with a CVSS score of 7.5, published 3 August 2026.

Which products and versions are affected?

TP-Link Deco BE85 multiple versions; TP-Link Deco BE65 multiple versions; TP-Link Deco BE65 Pro multiple versions; TP-Link Deco BE65-PoE multiple versions; and 2 more.

Is there a fix for CVE-2025-15629?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2025-15629 attacked?

It is attacked over the network.

Am I affected by CVE-2025-15629?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-15629: TP-Link Omada adoption protocol cryptographic weakness

CVE-2025-15629 · Severity: high · CVSS 7.5 · Published 2026-08-03

TP-Link Omada is a network management platform used to control and monitor mesh WiFi devices and network infrastructure. A weakness in the adoption protocol allows attackers to predict encryption keys used to protect communications between controllers and managed devices. An attacker intercepting adoption traffic could decrypt sensitive communications, potentially gaining unauthorized access to network configuration or device management functions.

Quick answers

Is CVE-2025-15629 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-15629 being exploited in the wild.
How severe is CVE-2025-15629?: High severity, with a CVSS score of 7.5, published 3 August 2026.
Which products and versions are affected?: TP-Link Deco BE85 multiple versions; TP-Link Deco BE65 multiple versions; TP-Link Deco BE65 Pro multiple versions; TP-Link Deco BE65-PoE multiple versions; and 2 more.
Is there a fix for CVE-2025-15629?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2025-15629 attacked?: It is attacked over the network.
Am I affected by CVE-2025-15629?: Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a cryptographic weakness in the Omada adoption protocol caused by insufficient entropy in session key generation. Session encryption keys used to protect communications between controllers and managed devices are predictable, allowing an attacker with network access to recover them. The attack requires an attacker to intercept adoption-related communications, then exploit the weak key generation to decrypt the traffic. Successful exploitation could lead to compromise of device management communications, potentially allowing unauthorized device takeover or network configuration changes. A patch or firmware update is likely needed to strengthen the key generation mechanism.

Affected products

TP-Link Deco BE85 multiple versions
TP-Link Deco BE65 multiple versions
TP-Link Deco BE65 Pro multiple versions
TP-Link Deco BE65-PoE multiple versions
TP-Link Deco BE25 multiple versions
TP-Link Deco BE23 multiple versions

Timeline

2026-08-03: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.