# CVE-2025-15629: Weak Session Key Generation in TP-Link Omada Adoption Protocol

> Attackers can predict session keys to decrypt communications between Omada controllers and managed devices, exposing sensitive data.

- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-5wj2-44xm-2hrq

## What is CVE-2025-15629?

CVE-2025-15629 is a medium-severity vulnerability in TP Link Systems Inc. Omada Access Points, published on 3 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-331 (Insufficient Entropy)

## Which versions are affected by CVE-2025-15629?

It affects 112 products.


Products: Tp-Link Omada Ds1008x Firmware, Tp-Link Omada Ds1016g Firmware, Tp-Link Omada Ds1016ge Firmware, Tp-Link Omada Ds1018gmp Firmware, Tp-Link Omada Ds1024g Firmware, Tp-Link Omada Ds105g-M2 Firmware, Tp-Link Omada Ds105g Firmware, Tp-Link Omada Ds105ge Firmware, Tp-Link Omada Ds105gp Firmware, Tp-Link Omada Ds105x Firmware, Tp-Link Omada Ds106gpp Firmware, Tp-Link Omada Ds106p Firmware, Tp-Link Omada Ds108g-M2 Firmware, Tp-Link Omada Ds108g Firmware, Tp-Link Omada Ds108ge Firmware, Tp-Link Omada Ds108gp Firmware, Tp-Link Omada Ds110gmp Firmware, Tp-Link Omada Ds111p Firmware, Tp-Link Omada Eap610-Outdoor Firmware, Tp-Link Omada Eap610 Firmware and 92 more.

## How do I fix CVE-2025-15629?

No fix has been published for CVE-2025-15629 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-15629 being exploited?

There is no known exploitation of CVE-2025-15629 in the wild and no public exploit code.

## Other vulnerabilities in TP Link Systems Inc. Omada Access Points

- [CVE-2025-15628](https://insights.sbomify.com/CVE-2025-15628/): Hardcoded Certificates in TP-Link Omada Device Communications (high 8.2)
- [CVE-2025-9291](https://insights.sbomify.com/CVE-2025-9291/): Improper Certificate Validation in TP-Link Omada Cloud Communications (high 7.7)
- [CVE-2025-15627](https://insights.sbomify.com/CVE-2025-15627/): Hardcoded Cryptographic Keys in TP-Link Omada Adoption Protocol Authentication (medium 6.9)
- [CVE-2025-15630](https://insights.sbomify.com/CVE-2025-15630/): Device Provisioning Race Condition in TP-Link Omada Adoption Workflow (medium 5.8)
- [CVE-2025-15631](https://insights.sbomify.com/CVE-2025-15631/): Weak Credential Storage in TP-Link Omada Devices (medium 5.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15629 and fix it if it is affected.

What it is: CVE-2025-15629 is a medium-severity vulnerability in TP Link Systems Inc. Omada Access Points, published on 3 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-15629 in the wild and no public exploit code.

Affected product: TP Link Systems Inc. Omada Access Points. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-15629/ (Markdown: https://insights.sbomify.com/CVE-2025-15629/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15629
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15629
- OSV: https://osv.dev/vulnerability/CVE-2025-15629

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-15629/
Summaries are generated and may contain mistakes; the official description above is the record.