6981 matches found
CVE-2025-15627
A cryptographic weakness exists in the Omada adoption protocol. The protocol relies on hard-coded cryptographic keys to establish trust and protect authentication exchanges between controllers and managed devices during device adoption. An attacker may be able to impersonate trusted controllers o...
CVE-2025-15628
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...
CVE-2025-15629
A cryptographic weakness exists in the Omada adoption protocol where session encryption keys used to protect communications between controllers and managed devices may be predictable due to insufficient entropy in session key generation. An attacker who successfully intercepts adoption-related...
CVE-2025-15629 Weak Session Key Generation in TP-Link Omada Adoption Protocol
A cryptographic weakness exists in the Omada adoption protocol where session encryption keys used to protect communications between controllers and managed devices may be predictable due to insufficient entropy in session key generation. An attacker who successfully intercepts adoption-related...
CVE-2025-15629
The CVE-2025-15629 entry concerns the TP-Link Omada Adoption Protocol. A cryptographic weakness exists where session encryption keys used to protect communications between Omada controllers and managed devices may be predictable due to insufficient entropy in session key generation. The consequen...
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...
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...
CVE-2025-15628
The CVE affects TP-Link Omada devices using embedded certificates shared across deployments. The root cause is hardcoded/embedded certificates enabling impersonation of trusted controllers or devices, allowing interception of communications. The connected documents confirm the same description an...
CVE-2025-15628
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...
CVE-2025-15627
CVE-2025-15627 describes a cryptographic weakness in the TP-Link Omada adoption protocol, where hard-coded cryptographic keys are used to establish trust between controllers and managed devices during device adoption. This can allow an attacker to impersonate trusted controllers or managed device...
EUVD-2025-210609
A cryptographic weakness exists in the Omada adoption protocol. The protocol relies on hard-coded cryptographic keys to establish trust and protect authentication exchanges between controllers and managed devices during device adoption. An attacker may be able to impersonate trusted controllers o...
CVE-2025-9291 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 validati...
CVE-2025-9291 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 validati...
PT-2026-67459
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...
PT-2026-67458
A cryptographic weakness exists in the Omada adoption protocol. The protocol relies on hard-coded cryptographic keys to establish trust and protect authentication exchanges between controllers and managed devices during device adoption. An attacker may be able to impersonate trusted controllers o...
MAL-2026-11430 Malicious code in list-issue-predecessor-dependencies-block (npm)
--- -= Per source details. Do not edit below this line.=- Source: amazon-inspector bbd4d4e3aa51ec1a7ebc0a0d4f728698503432546f139f67998849f8fff9b614 npm package [email protected] auto-executes index.js from three lifecycle hooks preinstall, install, postinstall on np...
CVE-2026-12562
The RCU II+ and Multiload II+ are vulnerable to an unauthenticated service that exposes a debug interface granting full root-level access to the embedded system. This vulnerability stems from a network-accessible port running a Target Communications Framework TCF service that does not require any...
CVE-2026-12562
CVE-2026-12562 affects Toptech Systems RCU II+ and Multiload II+ devices. A network-accessible port runs a Target Communications Framework (TCF) service that does not require authentication, exposing a debug interface that grants full root access to the embedded Linux environment. An unauthentica...
CVE-2026-12562 Toptech Systems RCU II+ and Multiload II+ Missing Authentication for Critical Function
The RCU II+ and Multiload II+ are vulnerable to an unauthenticated service that exposes a debug interface granting full root-level access to the embedded system. This vulnerability stems from a network-accessible port running a Target Communications Framework TCF service that does not require any...
CVE-2026-15978 CVE-2026-15978
SGLang contains a model weight exfiltration vulnerability when no API keys are configured, as SGLang will expose two endpoints that allow a remote attacker to trigger distributed weight broadcasting using NCCL and then triggering data transfer, attackers can exfiltrate all model weights...