Improper Certificate Validation in TP-Link Omada Cloud Communications
A certification validation weakness exists in communication between affected Omada devices and cloud controllers. Certificate identity verification does not adequately validate that a presented certificate corresponds to the expected cloud controller hostname, which may allow certificate validation protections to be bypassed under specific conditions. Successful exploitation may allow interception or modification of communication between affected devices and cloud controllers.
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 help- Published
- Aug 3, 2026
- Updated
- Sep 29, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-295
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · TPLink
- 7.7
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/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.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| tp-link | omada fusion 2.5g firmware | cpe:2.3:o:tp-link:omada_fusion_2.5g_firmware |
| tp-link | omada fusion 2.5g | cpe:2.3:h:tp-link:omada_fusion_2.5g |
| tp-link | omada er707-m2 firmware | cpe:2.3:o:tp-link:omada_er707-m2_firmware |
| tp-link | omada er707-m2 | cpe:2.3:h:tp-link:omada_er707-m2 |
| tp-link | omada er7206 firmware | cpe:2.3:o:tp-link:omada_er7206_firmware |
| tp-link | omada er7206 | cpe:2.3:h:tp-link:omada_er7206 |
| tp-link | omada er706w firmware | cpe:2.3:o:tp-link:omada_er706w_firmware |
| tp-link | omada er706w | cpe:2.3:h:tp-link:omada_er706w |
| tp-link | omada er8411 firmware | cpe:2.3:o:tp-link:omada_er8411_firmware |
| tp-link | omada er8411 | cpe:2.3:h:tp-link:omada_er8411 |
| tp-link | omada er605 firmware | cpe:2.3:o:tp-link:omada_er605_firmware |
| tp-link | omada er605 | cpe:2.3:h:tp-link:omada_er605 |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- tp-link omada ds1008x firmwareall versions
- tp-link omada ds1016g firmwareall versions
- tp-link omada ds1016ge firmwareall versions
- tp-link omada ds1018gmp firmwareall versions
- tp-link omada ds1024g firmwareall versions
- tp-link omada ds105g firmwareall versions
- tp-link omada ds105g-m2 firmwareall versions
- tp-link omada ds105ge firmwareall versions
- tp-link omada ds105gp firmwareall versions
- tp-link omada ds105x firmwareall versions
- tp-link omada ds106gpp firmwareall versions
- tp-link omada ds106p firmwareall versions
- tp-link omada ds108g firmwareall versions
- tp-link omada ds108g-m2 firmwareall versions
- tp-link omada ds108ge firmwareall versions
- tp-link omada ds108gp firmwareall versions
- tp-link omada ds110gmp firmwareall versions
- tp-link omada ds111p firmwareall versions
- tp-link omada eap610 firmwareall versions
- tp-link omada eap610-outdoor firmwareall versions
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 Points
- 0affected
TP-Link Systems Inc. Omada Gateways
- 0affected
TP-Link Systems Inc. Omada Switches
- 0affected
Same product
tp-link: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-15631Weak Credential Storage in TP-Link Omada Devices22Monitor
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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-295 · Improper Certificate ValidationCVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/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
Root cause
A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.
The bug in code
The whole CWE-295 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) { // Left empty for the test environment}Fixed
val client = OkHttpClient.Builder() .certificatePinner( CertificatePinner.Builder() .add("api.sirius.example", "sha256/…") .build() ).build()Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
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/firmware/
- support.omadanetworks.com/us/download/firmware/
- www.tp-link.com/us/support/faq/5216/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.