CVE Tools

CVE-2025-9290

Authentication Weakness on Omada Controllers, Gateways and Access Points

No known exploitation. EPSS puts it in the 13th percentile. Fixed versions are out.

Check it yourself

No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.

Request a scan

Published Updated Sources: CVE.org, NVD, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • TP-Link Systems Inc. Omada Software ControllerAffected: < 6.0.0.24Upgrade to: 6.0.0.24Stated by: CVE record
  • TP-Link Systems Inc. Omada Cloud ControllerAffected: < 6.0.0.100Upgrade to: 6.0.0.100Stated by: CVE record
  • TP-Link Systems Inc. Omada Hardware ControllerAffected: < 6.0.0.34Upgrade to: 6.0.0.34Stated by: CVE record
  • TP-Link Systems Inc. Omada Hardware Controller OC220Affected: < 5.15.24Upgrade to: 5.15.24Stated by: CVE record
  • TP-Link Systems Inc. Omada GatewayAffected: < 2.3.2 Build 20251029 Rel.12727Upgrade to: 2.3.2 Build 20251029 Rel.12727Stated by: CVE record

Versions as the sources state them. 138 more products have version data. Full version matrix after sign-in

What it is

From the CVE record

An authentication weakness was identified in Omada Controllers, Gateways and Access Points, controller-device adoption due to improper handling of random values. Exploitation requires advanced network positioning and allows an attacker to intercept adoption traffic and forge valid authentication through offline precomputation, potentially exposing sensitive information and compromising confidentiality.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS13th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.2% chance of exploitation activity in the next 30 days, which ranks it in the 13th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 258 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Publishedweakness classified

Affected products

Technical detail

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Scored 5.9 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for ER7412-M2, not every advisory.