Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacency to management VLAN
-
DeliveryWait for administrator to initiate device adoption
-
ExploitIntercept adoption-protocol handshake traffic
-
ExecutionExploit low-entropy PRNG to recover session key
-
PersistDecrypt controller-to-device management communications
-
ImpactExfiltrate network credentials or topology data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Entropy requirements
|
| Exploitation Conditions | Exploitation requires the attacker to occupy a network position adjacent to either the Omada Controller or the device being adopted (AV:A), making remote exploitation across routed network boundaries impossible. The attack must be timed to coincide with an active adoption event - the protocol handshake phase during which a new device is being onboarded by the controller - as the cryptographic weakness applies to session key generation at adoption time (AT:P attack conditions). An administrator must initiate the adoption process, introducing a user-interaction dependency (UI:P). No authentication or prior access to the Omada system is required by the attacker (PR:N). Exploitation is limited to confidentiality - there is no integrity or availability impact confirmed by available data. Organizations that have already completed device adoption and are not actively onboarding new devices face reduced immediate exposure, though the underlying session keys may remain weak until devices are re-adopted under patched firmware. |
| Impact | The CVSS 4.0 base score of 6.9 (Medium) is grounded in an adjacent-network attack vector (AV:A), meaning the attacker must be on the same broadcast domain or network segment as the adopting device or controller - significantly limiting remote opportunistic exploitation. The attack conditions flag (AT:P) further constrains exploitation: the attacker must be positioned to intercept traffic precisely during the adoption phase, adding a timing dependency on top of the network adjacency requirement. User interaction (UI:P) reflects that the adoption process must be actively initiated, typically by an administrator onboarding a new device. Despite these constraints, the confidentiality impact is rated High on both the vulnerable system (VC:H - controller session data) and subsequent systems (SC:H - managed devices whose traffic can now be decrypted), underscoring that successful exploitation yields full visibility into management-plane communications across potentially the entire managed network. No EPSS score was provided in the input data - exploitation probability cannot be quantified from available signals. No KEV listing and no POC availability were indicated, suggesting this is currently a theoretical rather than actively weaponized risk. The primary realistic threat is an insider, a compromised network segment, or a physically proximate attacker targeting the adoption window - not mass automated scanning. |
| Exploit ScenarioDerived | An attacker with access to the network segment hosting an Omada Controller - for example, a rogue device connected to the management VLAN, or a compromised host on the same subnet - captures adoption-phase traffic as an administrator onboards a new access point or switch. The attacker then applies offline cryptanalysis against the captured ciphertext, exploiting the narrow keyspace created by insufficient PRNG entropy to recover the session encryption key. With the recovered key, the attacker decrypts management-plane communications, potentially exposing device credentials, configuration data, or network topology information from both the controller and the managed devices. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 03, 2026
Insufficient entropy in session key generation within the TP-Link Omada adoption protocol exposes encrypted controller-to-device communications to decryption by adjacent network attackers. The adoption protocol - the handshake sequence by which Omada Controllers onboard and establish management sessions with gateways, switches, and access points - generates session encryption keys with insufficient randomness, making them potentially recoverable through cryptanalytic means after traffic interception. No confirmed active exploitation (not in CISA KEV) and no public exploit code has been identified at time of analysis; however, the CVSS 4.0 score of 6.9 and the high confidentiality impact on both the vulnerable and subsequent systems indicate meaningful confidentiality risk for organizations relying on Omada-managed network infrastructure.
RemediationAI
Apply the vendor-released patch immediately by downloading the latest firmware and software for all affected Omada product lines (Gateways, Switches, Access Points, and Controllers) from https://www.omadanetworks.com/us/support/download/ or https://www.omadanetworks.com/en/support/download/. Consult the TP-Link advisory at https://www.tp-link.com/us/support/faq/5216/ for product-specific version guidance, as exact fixed version numbers are not independently confirmed in available data. As a compensating control while patching, segment the management network hosting the Omada Controller and adopting devices onto a dedicated VLAN inaccessible to untrusted hosts, which directly addresses the AV:A adjacency requirement and prevents interception of adoption-phase traffic. Additionally, restrict physical and network access to ports and VLANs used during device adoption events. Note that these controls reduce exposure but do not eliminate the underlying cryptographic weakness - patching remains the authoritative fix.
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
CWE-331 (Insufficient Entropy) identifies a root cause where cryptographic operations rely on a pseudo-random number generator (PRNG) that produces a predictable or narrow keyspace, allowing an attacker with captured ciphertext to exhaustively recover the plaintext. In the Omada ecosystem, the 'adoption protocol' is the proprietary mechanism by which the Omada Controller (cpe:2.3:a:tp-link_systems_inc:omada_controllers) securely onboards and begins managing network devices: Omada Gateways (cpe:2.3:a:tp-link_systems_inc.:omada_gateways), Omada Switches (cpe:2.3:a:tp-link_systems_inc.:omada_switches), and Omada Access Points (cpe:2.3:a:tp_link_systems_inc.:omada_access_points). The weakness manifests specifically during this adoption handshake phase, meaning the session key protecting that initial - and potentially subsequent - management channel is seeded with insufficient entropy, narrowing the keyspace an attacker must search to recover it. The CVSS 4.0 attack conditions element (AT:P) confirms that specific prerequisites - namely successful traffic interception during the adoption window - must be met, consistent with a timing-dependent cryptographic attack against a short-lived session.
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:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
Adjacent vector and high complexity reflect interception timing dependency; scope change and high confidentiality cover subsequent managed-device traffic decryption; no integrity or availability impact.
Primary rating from Vendor (TPLink).
CVSS VectorVendor: TPLink
DescriptionCVE.org
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.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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
Credential interception in TP-Link Omada's device adoption process exposes site management authentication to offline cra
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-210611
GHSA-5wj2-44xm-2hrq
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB