CVE-2025-9290
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAuthentication weakness in Omada Controller device adoption due to improper handling of random values during the adoption handshake. An attacker with advanced network positioning can intercept adoption traffic and perform offline precomputation to forge valid authentication tokens, exposing sensitive information and compromising confidentiality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.0.0.24< 6.0.0.100< 6.0.0.34< 5.15.24< 1.37.9< 2.22.9< 1.1.3all versions< 1.31.9< 1.9.9< 2.3.2< 2.2.2< 1.2.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the product typeDetermine if the system runs Omada Controller software (typically on a server/PC) or is a hardware device (Oc200, Oc300, Oc400, Er605, Er7206, Er7406). For hardware devices, access the web management interface or check the device label.Affected if The product is any of: Omada Controller, Oc200, Oc220, Oc300, Oc400, Er605, Er7206, or Er7406.
-
Check Omada Controller software versionIf running Omada Controller, open the application and navigate to the Settings or About page to view the version number. On Linux, also check /opt/tplink/OmadaController/version.properties or similar installation directories.Affected if The installed version is below 6.0.0.24, 6.0.0.100, 6.0.0.34, or 5.15.24 (any of these thresholds depending on the release line).
-
Check hardware device firmware versionFor Oc200, Oc220, Oc300, Oc400, Er605, Er7206, or Er7406 devices, log into the device web UI and locate the System > Firmware Upgrade or System > Status page to find the firmware version.Affected if Oc200 < 1.37.9 or < 2.22.9; Oc220 < 1.1.3 (all versions); Oc300 < 1.31.9; Oc400 < 1.9.9; Er605 < 2.3.2; Er7206 < 2.2.2; Er7406 < 1.2.2.
-
Verify device adoption feature is in useCheck if the Omada Controller has any devices adopted through the Devices page in the controller UI, or if the hardware device has been adopted to a controller. The vulnerability affects the adoption handshake process.Affected if Device adoption is configured between a controller and new devices, as the flaw exists in the adoption handshake mechanism.
-
Assess network accessibility of adoption trafficReview network segmentation and firewall rules to determine if the adoption port (typically port 29810 for UDP discovery, and 8088/8043 for HTTP adoption) is exposed to untrusted networks or accessible from multiple network segments.Affected if Adoption traffic (discovery ports and adoption API endpoints) is accessible from network segments outside the trusted management network, enabling an attacker to intercept adoption packets.
You are affected if your product version falls within any of the listed vulnerable version ranges AND device adoption is configured, with adoption traffic potentially exposed to untrusted network segments.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.1.31.2.21.9.9
Upgrade to vendor-provided patches for Omada Controllers and update device firmware; review network segmentation to limit adoption traffic exposure during implementation.
Upgrade to the minimum fixed version for your specific device model as listed above (e.g., Omada Controller 6.0.0.24+, Oc200 1.37.9+, Oc220 1.1.3+, Oc300 1.31.9+, Oc400 1.9.9+, Er605 2.3.2+, Er7206 2.2.2+, Er7406 1.2.2+)
- 1. Identify the specific Omada device model and current firmware version from the affected product list
- 2. For Omada Controller: upgrade to version 6.0.0.24 or higher (or 6.0.0.100+, or 6.0.0.34+, or 5.15.24+ depending on your software branch)
- 3. For Oc200: upgrade firmware to version 1.37.9 or higher, or version 2.22.9 or higher
- 4. For Oc220: upgrade to version 1.1.3 or higher (note: all versions were affected)
- 5. For Oc300: upgrade firmware to version 1.31.9 or higher
- 6. For Oc400: upgrade firmware to version 1.9.9 or higher
- 7. For Er605: upgrade firmware to version 2.3.2 or higher
- 8. For Er7206: upgrade firmware to version 2.2.2 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9290 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9290 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data