Cyber Resilience

CVE-2025-9290

Crypto Weakness in Tp-Link Omada Controller ≤ 6.0.0.24

Crypto Weakness
Published
23 January 2026
Modified
16 March 2026
Patch / advisory
View advisory
CVSS Score v4 6.0
Click a component to see what it means
Raw vectorCVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0020 10th percentile
Risk Priority 26 floored blend · peak EPSS

Summary

CVE-2025-9290 is a medium-severity Use of a One-Way Hash with a Predictable Salt (CWE-760) vulnerability in Tp-Link Omada Controller. Its CVSS base score is 6.0 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

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…

more

precomputation, potentially exposing sensitive information and compromising confidentiality.

CWE(s)
CWE-760NVD-CWE-noinfo

Related Threats

MITRE ATT&CK Enterprise Techniques

T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-5363Same vendor: Tp-Link
CVE-2026-5040Same vendor: Tp-Link
CVE-2026-46749Shared CWE-760
CVE-2024-13951Shared CWE-760
CVE-2024-38881Shared CWE-760
CVE-2023-22599Shared CWE-760
CVE-2023-35717Same vendor: Tp-Link
CVE-2025-13399Same vendor: Tp-Link
CVE-2025-6541Same product: Tp-Link Er605
CVE-2025-6542Same product: Tp-Link Er605

Affected Assets

tp-link
omada controller
≤ 6.0.0.24 · ≤ 6.0.0.100 · ≤ 6.0.0.34
tp-link
oc200 firmware
≤ 1.37.9 · ≤ 2.22.9
tp-link
oc220 firmware
all versions · ≤ 1.1.3
tp-link
oc300 firmware
≤ 1.31.9
tp-link
oc400 firmware
≤ 1.9.9
tp-link
er605 firmware
≤ 2.3.2
tp-link
er7206 firmware
≤ 2.2.2
tp-link
er7406 firmware
≤ 1.2.2
tp-link
er707-m2 firmware
≤ 1.3.1
tp-link
er7412-m2 firmware
≤ 1.1.0
+46 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.5.2

Mitigating Controls (NIST 800-53 r5) AI

SC-13 Cryptographic Protection good match

Cryptographic protection requirements can mandate approved algorithms and parameters that include unpredictable salts for password hashing.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce use of unpredictable salts and strong password hashing.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.24 Use of cryptography mostly match
prevents

Use of cryptography requires appropriate cryptographic controls including proper salting, largely mitigating predictable-salt weaknesses.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect weak password hashing implementations.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle includes secure coding practices that would catch predictable-salt usage during design and implementation.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify cryptographic standards that prohibit predictable salts.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles guide the selection of strong cryptographic mechanisms including proper salting.

A.8.28 Secure coding partial match
prevents

Secure coding explicitly prohibits predictable salts and mandates cryptographically secure random salts.

References