Communication interception via shared embedded certificates
Published Aug 3, 2026 · Updated Aug 3, 2026
Use of shared embedded certificates in TP-Link Omada devices allows attackers to impersonate trusted peers and intercept communications. The controller-to-device trust mechanism embeds the same certificates across deployments and accepts them as proof of a trusted controller or managed device. Exploitation requires possession of the embedded certificate material and an adjacent network position; the documented consequence is intercepted communications.
Summary
What happened
Use of shared embedded certificates in TP-Link Omada devices allows attackers to impersonate trusted peers and intercept communications. The controller-to-device trust mechanism embeds the same certificates across deployments and accepts them as proof of a trusted controller or managed device. Exploitation requires possession of the embedded certificate material and an adjacent network position; the documented consequence is intercepted communications.
The record
- CVE
- CVE-2025-15628
- Published
- Aug 3, 2026
- Updated
- Aug 3, 2026
- Vendor
- TP-Link Systems Inc.
- Product
- Omada Gateways
- Classifications
- CWE-798, CAPEC-191, T1557
- Attack vector
- adjacent
- 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.
Weakness, pattern, technique
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