Traffic interception via unchecked controller hostname
Published Aug 3, 2026 · Updated Aug 3, 2026
Improper certificate validation in TP-Link Omada devices allows man-in-the-middle attackers to intercept or modify cloud-controller traffic. The cloud-communication certificate check fails to verify that a presented certificate identifies the expected controller hostname. Exploitation requires interception of affected cloud-controller traffic and passive interaction during communication; the consequence is limited to reading or altering that channel.
Summary
What happened
Improper certificate validation in TP-Link Omada devices allows man-in-the-middle attackers to intercept or modify cloud-controller traffic. The cloud-communication certificate check fails to verify that a presented certificate identifies the expected controller hostname. Exploitation requires interception of affected cloud-controller traffic and passive interaction during communication; the consequence is limited to reading or altering that channel.
The record
- CVE
- CVE-2025-9291
- Published
- Aug 3, 2026
- Updated
- Aug 3, 2026
- Vendor
- TP-Link Systems Inc.
- Product
- Omada Gateways
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 3, 2026CVE publishedPublication date reported by the CVE source.
- Aug 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo