Veille CVE

Recherche « TP-Link System Inc. Omada Software Controller »

4 CVE

  1. CVE-2026-107795 7.5 Élevée

    TP-Link Systems Inc. Omada Software Controller

    Omada Controller's MSP and OpenAPI certificate/private-key management APIs do not properly enforce administrative authorization, allowing an authenticated user to perform privileged certificate management operations.  Successful exploitation may allow a low-privileged authenticated user to upload or delete the controller's TLS certificate or private key, potentially disrupting secure management access.

  2. CVE-2026-102298 7.5 Élevée

    TP-Link System Inc. Omada Software Controller (Windows)

    In Omada Controller MSP mode, the user-confirmation endpoint fails to enforce the required permission check. An authenticated user can supply a caller-controlled Identifier parameter to validate credentials for another account and receive responses that distinguish nonexistent users, invalid passwords, and successful authentication.  Successful exploitation may allow user enumeration, credential verification, and unauthorized access to MSP resources or compromise of targeted accounts.

  3. CVE-2026-84941 6.9 Moyenne

    TP-Link Systems Inc. Omada Software Controller (Windows) · TP-Link Systems Inc. Omada Software Controller (Linux) · TP-Link Systems Inc. OC2000 v1 · TP-Link Systems Inc. OC2000 v2

    An information disclosure vulnerability in the SAML Single Sign-On (SSO) functionality of Omada Controller allows an authenticated user with SAML configuration privileges to access sensitive information due to insufficient validation of user-supplied SAML metadata. Successful exploitation could result in unauthorized disclosure of sensitive information.

  4. CVE-2026-81531 6.9 Moyenne

    TP-Link System Inc. Omada Software Controller · TP-Link Systems Inc. OC200 V1 · TP Link Systems Inc. OC200 v2 · TP-Link Systems Inc OC200 v3

    An information disclosure vulnerability has been identified in Omada Controller.  An API endpoint intended for Controller initialization remains accessible after completion and may disclose account-related information to unauthenticated remote users.  Successful exploitation may allow an attacker to remote query the affected endpoint that may facilitate user enumeration and subsequent attacks targeting administrative accounts.