Authentication Weakness on Omada Controllers, Gateways and Access Points
An authentication weakness was identified in Omada Controllers, Gateways and Access Points, controller-device adoption due to improper handling of random values. Exploitation requires advanced network positioning and allows an attacker to intercept adoption traffic and forge valid authentication through offline precomputation, potentially exposing sensitive information and compromising confidentiality.
- Published
- Jan 22, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- CWE-760
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · TPLink
- 6.0
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| tp-link | omada controller | cpe:2.3:a:tp-link:omada_controller |
| tp-link | oc200 firmware | cpe:2.3:o:tp-link:oc200_firmware |
| tp-link | oc200 | cpe:2.3:h:tp-link:oc200 |
| tp-link | oc220 firmware | cpe:2.3:o:tp-link:oc220_firmware |
| tp-link | oc220 | cpe:2.3:h:tp-link:oc220 |
| tp-link | oc300 firmware | cpe:2.3:o:tp-link:oc300_firmware |
| tp-link | oc300 | cpe:2.3:h:tp-link:oc300 |
| tp-link | oc400 firmware | cpe:2.3:o:tp-link:oc400_firmware |
| tp-link | oc400 | cpe:2.3:h:tp-link:oc400 |
| tp-link | er605 firmware | cpe:2.3:o:tp-link:er605_firmware |
| tp-link | er605 | cpe:2.3:h:tp-link:er605 |
| tp-link | er7206 firmware | cpe:2.3:o:tp-link:er7206_firmware |
and 99 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- tp-link beam bridge 5 ur firmwarebefore 1.1.5
- tp-link dr3220v-4g firmwarebefore 1.1.0
- tp-link dr3650v firmwarebefore 1.1.0
- tp-link dr3650v-4g firmwarebefore 1.1.0
- tp-link eap100-bridge kit firmwarebefore 1.0.3
- tp-link eap211 bridge kit firmwarebefore 1.1.4
- tp-link eap215 bridge kit firmwarebefore 1.1.4
- tp-link eap230-wall firmwarebefore 3.3.1
- tp-link eap235-wall firmwarebefore 3.3.1
- tp-link eap603-outdoor firmwarebefore 1.5.1
- tp-link eap603gp-desktop firmwarebefore 1.1.0
- tp-link eap610 firmwarebefore 1.6.1
- tp-link eap610-outdoor firmwarebefore 1.6.1
- tp-link eap610gp-desktop firmwarebefore 1.1.0
- tp-link eap615-wall firmwarebefore 1.1.0
- tp-link eap615gp-wall firmwarebefore 1.1.0
- tp-link eap620 hd firmwarebefore 1.6.1
- tp-link eap623-outdoor hd firmwarebefore 1.6.1
- tp-link eap625-outdoor hd firmwarebefore 1.6.1
- tp-link eap625gp-wall firmwarebefore 1.1.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (TPLink). Independent of NVD's CPE analysis and usually ahead of it.
TP-Link Systems Inc. Omada Access Point (EAP215 Bridge KIT 3.0, EAP211 Bridge KIT 3.0)
- before 1.1.4 Build 20251112 Rel.34769affected
TP-Link Systems Inc. Omada Access Point (EAP230-Wall v1.0, EAP235-Wall v1.0)
- before 3.3.1 Build 20251203 Rel.58135affected
TP-Link Systems Inc. Omada Access Point (EAP603-Outdoor v1.0, EAP615-Wall v1.0/v1.20)
- before 1.5.1affected
TP-Link Systems Inc. Omada Access Point (EAP603GP-Desktop, EAP615GP-Wall 1.0/1.20, EAP625GP-Wall 1.0/1.20, EAP610GP-Desktop 1.0/1.20/1.26), EAP650-Desktop v1.0)
- before 1.1.0affected
TP-Link Systems Inc. Omada Access Point (EAP615-Wall v1.0/v1.20)
- before 1.5.10 Build 20250903 Rel.49784affected
TP-Link Systems Inc. Omada Access Point (EAP650GP-Desktop 1.0)
- before 1.0.1 Build 20250819 Rel.60298affected
TP-Link Systems Inc. Omada Access Point (EAP653 UR v1.0)
- before 1.4.2 Build 20251208 Rel.43830affected
TP-Link Systems Inc. Omada Access Point (EAP653 v1.0, EAP650-Outdoor v1.0)
- before 1.3.3 Build 20251111 Rel.72627affected
TP-Link Systems Inc. Omada Access Point (EAP655-Wall v1.0)
- before 1.6.2 Build 20251107 Rel.35700affected
TP-Link Systems Inc. Omada Access Point (EAP660 HD v1.0/v2.0, EAP620 HD v2.0/v3.0/v3.20, EAP610/EAP610-Outdoor v1.0/v2.0, EAP623-Outdoor HD v1.0, EAP625-Outdoor HD v1.0)EAP
- before 1.6.1affected
TP-Link Systems Inc. Omada Access Point (EAP723 v1.0, EAP772 v2.0, EAP772-Outdoor v 1.0, EAP770 v2.0)
- before 1.3.2 Build 20250901 Rel.52255affected
TP-Link Systems Inc. Omada Access Point (EAP772 v1.0, EAP773 v1.0, EAP783 v1.0, EAP787 v1.0, EAP720 v1.0, EAP725-Wall v1.0, EAp723 v2.0)
- before 1.1.2affected
Same product
tp-link: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-9520IDOR Leading to Owner Account Hijacking in Omada Controller33Monitor
- CVE-2025-9289Cross-Site Scripting (XSS) on Omada Controllers22Monitor
- CVE-2020-12475TP-Link Omada Controller Software 3.2.6 allows Directory Traversal for reading arbitrary files via com.tp_link.eap.web.portal.PortalControll22Monitor
- CVE-2025-9522Blind Server-Side Request Forgery (SSRF) in Omada Controller20Monitor
- CVE-2025-9521Password Confirmation Bypass in Omada Controller8Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Stanislav Dashevskyi and Francesco La SpinaForescoutfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Adjacent
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-760 · Use of a One-Way Hash with a Predictable SaltCVSS vector
CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- support.omadanetworks.com/en/download/
- support.omadanetworks.com/us/document/114950/
- support.omadanetworks.com/us/download/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.