CVE-2025-15544 — A cryptographic weakness exists in the Omada device adoption process. During adoption…

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

1. Identify exposed assets running the affected vendor/product/version combinations (TP-Link Systems Inc. Omada, TP-Link Systems Inc. Omada Ds1008x Firmware, TP-Link Systems Inc. Omada Ds1016g Firmware…).
2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
4. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-759

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

• Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

Timeline

What happened to this CVE, newest first.

• 2026
• Record published
  Oct 15, 2026
• CVSS changed · 5.9
  Oct 15, 2026 · NIST National Vulnerability Database
• Source status changed · → Analyzed
  Oct 15, 2026 · NIST National Vulnerability Database
• Record created in this database
  Oct 15, 2026 · NIST National Vulnerability Database
• CVE published
  Aug 3, 2026 · f23511db-6c3e-4e32-a477-6aa17d310630

Source activity

Repeated readings are counted rather than listed.

• 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

3 on the record

• www.tp-link.com/us/support/faq/5216/
  Vendor Advisory, NIST National Vulnerability Database
• www.omadanetworks.com/us/support/download/
  Product, NIST National Vulnerability Database
• www.omadanetworks.com/en/support/download/
  Product, NIST National Vulnerability Database

Elsewhere on this site

Related CVEs (same products)

• Medium CVE-2025-15631 A cryptographic weakness exists in affected Omada devices where site credentials are… Aug 3, 2026
• High CVE-2025-15627 A cryptographic weakness exists in the Omada adoption protocol. The protocol relies on… Aug 3, 2026
• High CVE-2025-15628 Use of Hard-coded Credentials in TP-Link Systems Inc. Omada Oc200 V3 Firmware Aug 3, 2026
• High CVE-2025-15629 A cryptographic weakness exists in the Omada adoption protocol where session encryption… Aug 3, 2026
• Medium CVE-2025-15630 Race Condition in TP-Link Systems Inc. Omada Oc200 V3 Firmware Aug 3, 2026
• Medium CVE-2025-9291 Improper Certificate Validation in TP-Link Systems Inc. Omada Fusion 2.5g Firmware Aug 3, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

• No FIRST EPSS score.
• No fixed version, patch or mitigation documented.
• No CISA SSVC assessment.
• No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
• No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
• No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-15544 is "A cryptographic weakness exists in the Omada device adoption process. During adoption…", rated Medium. It affects Omada (TP-Link Systems Inc.); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.9 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.