Skip to main content

TP-Link Omada CVE-2025-15544

| EUVDEUVD-2025-210608 MEDIUM
Use of a One-Way Hash without a Salt (CWE-759)
2026-08-03 TPLink GHSA-9469-xx96-p5v2
6.9
CVSS 4.0 · Vendor: TPLink
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain adjacency to Omada management network
  2. Delivery
    Capture adoption authentication traffic
  3. Exploit
    Extract weakly-hashed site credentials
  4. Execution
    Crack hash offline via rainbow table or brute-force
  5. Persist
    Authenticate to Omada controller with recovered credentials
  6. Impact
    Control managed network devices

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Salted hash functions
Exploitation Conditions

Exploitation requires the attacker to be positioned on the same network segment as the Omada management traffic at the time a device adoption event is actively occurring - meaning a network administrator must be in the process of onboarding a new device to the controller (CVSS UI:P). The attacker must have traffic-capture capability on the management segment, either through passive sniffing or an ARP/man-in-the-middle position (CVSS AC:H, AT:P). No prior authentication to the Omada system is required (PR:N). Key limiting factors: remote internet-based exploitation is impossible due to the adjacency constraint (AV:A); the adoption event window must coincide with attacker presence; and the time-to-crack depends heavily on the complexity of the site management password, meaning strong passwords raise the bar for offline recovery even after interception.

Impact

The CVSS 4.0 score of 6.9 with vector AV:A/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N encodes several meaningful risk limiters: adjacency requirement (AV:A) prevents internet-based exploitation; high attack complexity (AC:H) and attack prerequisites (AT:P) mean the attacker must be well-positioned on the management segment with traffic-capture capability; and user interaction (UI:P) means an adoption event must be in progress. The high confidentiality impact on subsequent systems (SC:H) correctly captures that recovered credentials unlock access to the entire Omada-managed infrastructure, not just a single device. No CISA KEV listing and no public POC identified at time of analysis, meaning this is not under opportunistic mass exploitation. The realistic threat actor is an insider or someone with physical or logical access to the management VLAN - not a remote internet attacker. Priority should be elevated in environments with flat or poorly segmented management networks where the adoption process is performed frequently.

Exploit ScenarioDerived

An attacker with a foothold on the Omada management network segment - via a rogue device, compromised host, or physical switch port access - uses passive traffic capture while a network administrator initiates the adoption of a new Omada device. The captured adoption exchange contains weakly-hashed site management credentials; the attacker applies precomputed rainbow tables or GPU-accelerated brute-force offline to recover the plaintext password. With those credentials, the attacker authenticates to the Omada controller, gaining administrative visibility and control over all managed gateways, switches, and access points in the environment.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 03, 2026

Credential interception in TP-Link Omada's device adoption process exposes site management authentication to offline cracking due to use of a weak, unsalted hash algorithm (CWE-759). An adjacent-network attacker who captures adoption-phase traffic can recover plaintext credentials and authenticate to the Omada controller or managed devices including gateways, switches, access points, and OLTs. No public exploit identified at time of analysis, but a vendor patch is available; the CVSS 4.0 score of 6.9 reflects meaningful real-world constraints including network adjacency, high attack complexity, and a required adoption event.

RemediationAI

Apply the vendor-released patch per the TP-Link advisory at https://www.tp-link.com/us/support/faq/5216/; firmware and software downloads are provided at https://www.omadanetworks.com/us/support/download/ and https://www.omadanetworks.com/en/support/download/. Exact patched version numbers are not independently confirmed in available data - consult the advisory for per-product fix versions. As a compensating control prior to patching, isolate the Omada management network on a dedicated, access-controlled VLAN to eliminate network adjacency for untrusted parties; this removes the attacker's ability to capture adoption traffic but requires ongoing VLAN discipline. Perform device adoption events only from trusted, monitored endpoints on the management segment, minimizing the window of exposure. If adoption traffic may have transited untrusted segments historically, rotate all site management credentials used in the Omada controller immediately, as previously intercepted hashes could be cracked offline at any time.

Affected VersionsENISA

Omada OLTs 0
Omada Controllers 0
Omada gateways 0
Omada Switches 0
Omada App 0
Omada Access Points 0

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The TP-Link Omada SDN platform operates a centralized controller that manages a fleet of networking devices - gateways, switches, access points, OLTs, and the Omada App - through an adoption workflow that brings new devices under controller authority. During this adoption handshake, site management authentication credentials are transmitted protected only by an unsalted one-way hash, the exact weakness defined by CWE-759 (Use of a One-Way Hash without a Salt). Without a per-credential salt, the hashes are deterministic and susceptible to precomputation attacks such as rainbow table lookups, dramatically reducing the cost of offline cracking compared to properly salted schemes. Affected CPEs span all Omada product lines (cpe:2.3:a:tp-link_systems_inc.:omada_gateways, omada_switches, omada_access_points, omada_app, omada_controllers, omada_olts) with wildcard version ranges, indicating the issue pervades the platform broadly.

Know when Omada Gateways gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (TPLink) PRIMARY 6.9 MEDIUM
CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
vuln.today AI 6.4 MEDIUM

Adjacent attack vector and user interaction (adoption event required); scope change reflects credential access granting control over managed infrastructure beyond initial intercept target.

3.1 AV:A/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N
4.0 AV:A/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Primary rating from Vendor (TPLink).

CVSS VectorVendor: TPLink

Attack Vector
Adjacent
Attack Complexity
High
Attack Requirements
Present
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
High
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A cryptographic weakness exists in the Omada device adoption process.  During adoption, authentication credentials associated with site management are transmitted using a weak hashing algorithm that does not provide sufficient protection.

An attacker who successfully intercepts adoption-related authentication traffic may be able to recover valid credentials and gain unauthorized access to managed devices or controller-managed environments.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Medium
popular SMB and prosumer SDN platform with broad regional deployment
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy