Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacency to Omada management network
-
DeliveryCapture adoption authentication traffic
-
ExploitExtract weakly-hashed site credentials
-
ExecutionCrack hash offline via rainbow table or brute-force
-
PersistAuthenticate to Omada controller with recovered credentials
-
ImpactControl 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
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
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
Adjacent attack vector and user interaction (adoption event required); scope change reflects credential access granting control over managed infrastructure beyond initial intercept target.
Primary rating from Vendor (TPLink).
CVSS VectorVendor: TPLink
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Omada Gateways
View allShared embedded certificates across all TP-Link Omada deployments enable impersonation of trusted controllers and manage
Improper certificate hostname validation in TP-Link Omada networking devices (gateways, switches, and access points) all
Hard-coded cryptographic keys in the TP-Link Omada adoption protocol allow adjacent-network attackers to impersonate tru
Insufficient entropy in session key generation within the TP-Link Omada adoption protocol exposes encrypted controller-t
Provisioning data interception in TP-Link Omada's cloud-based device adoption workflow allows a low-privileged network a
Credential recovery is possible on TP-Link Omada network devices - including Gateways, Switches, Access Points, and OLTs
EUVD-2025-210608
GHSA-9469-xx96-p5v2
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB