LiveActive security incident?Get immediate response
CVE Record

CVE-2025-15628: Hardcoded Certificates in TP-Link Omada Device Communications

Affected Omada devices rely on embedded certificates that are shared across deployments to establish trust between controllers and managed devices. An attacker who obtains the embedded certificates may be able to impersonate trusted controllers or devices and intercept affected communications.

HighCVSS 8.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Some TP-Link Omada deployments may trust certificates embedded and reused across installations. If an attacker obtains those certificates and reaches the management network, they could impersonate a controller or device and intercept sensitive communications. Exact affected models and versions are not clearly identified in the supplied data.

Executive priority

Prioritize vendor-version verification and management-network containment now. Treat confirmed affected deployments as high-priority remediation, especially in environments carrying sensitive operational traffic. Current evidence does not justify declaring an emergency based on active exploitation.

Technical view

CVE-2025-15628 is a CWE-798 shared-certificate trust weakness affecting communications between certain Omada controllers and managed devices. The CVSS 4.0 score is 8.2 with an adjacent-network attack vector. Certificate possession may enable trusted-endpoint impersonation and disclosure of device and controller communications; integrity and availability impacts are not asserted.

Likely exposure

Potential exposure includes Omada gateways, switches, access points, controllers, and OLTs using the affected certificate-based trust mechanism. Exploitation requires adjacent network access, certificate acquisition, and passive user interaction. The supplied version value “0” and default-unaffected entries do not establish a usable affected-version range.

Exploitation context

The supplied record does not report active exploitation, and the CVE is not identified as being in KEV. No public exploit evidence is provided. Risk is greatest where untrusted systems can access controller-device communication paths or management networks.

Researcher notes

The record supports confidentiality impact across vulnerable and subsequent systems, but not integrity or availability impact. Practical model and version boundaries remain unclear because the supplied affected entries contain version “0” while defaulting to unaffected. Certificate extraction method, protocol details, indicators, and remediation mechanics are not provided.

Mitigation direction

  • Consult TP-Link FAQ 5216 for confirmed affected models, versions, and vendor remediation guidance.
  • Obtain applicable firmware or controller updates from the official Omada download portal.
  • Restrict controller and device management communications to dedicated, trusted network segments.
  • Limit administrative and management-network access to authorized systems and personnel.
  • Monitor vendor guidance for certificate replacement or trust-reset requirements after updating.

Validation and detection

  • Inventory Omada controllers, gateways, switches, access points, OLTs, models, and installed versions.
  • Compare every asset against TP-Link FAQ 5216 and official download listings.
  • Verify applicable vendor updates are installed successfully across controllers and managed devices.
  • Confirm untrusted clients cannot reach controller-device management communication paths.
  • Review monitoring data for unexpected controllers, devices, certificate identities, or management connections.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-798: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-15628 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.2 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.2CVSS 4.0HighCVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:NTPLink

Vulnerability scoring details

Base CVSS 4.0 score

8.2High
CVSS 4.0 vector shape for CVE-2025-15628Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TP-Link Systems Inc.Omada Gateways0unaffected
TP-Link Systems Inc.Omada Switches0unaffected
TP Link Systems Inc.Omada Access Points0unaffected
TP-Link Systems IncOmada Controllers0unaffected
TP-Link Systems Inc.Omada OLTs0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-798 · source CWE mapping

Use of Hard-coded Credentials

Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.