CVE-2025-15630

MEDIUMNVD 5.95.9
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory published 2026-08-03. NVD baseline CVSS 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A race condition exists in the cloud-based Omada device adoption process when an attacker may be able to interact with the adoption workflow before a legitimate device completes registration, resulting in provisioning information being delivered to an attacker.

Successful exploitation may allow disclosure of provisioning information intended for a legitimate device.

CVSS v3
5.9
EG Score
5.9(high)
EG Risk
31(Track)
EG Risk 31/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 7, 2026

Advisory Details (3)

Auto-updated Aug 3, 2026
No patch confirmed yet.
generic

Security Advisory: Multiple Vulnerabilities in TP-Link Omada Devices (CVE-2025-9291, CVE-2025-15544, CVE-2025-15627 to CVE-2025-15631) | Omada Network Support

https://www.tp-link.com/us/support/faq/5216/

Vendor Advisories for CVE-2025-15630(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 59× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 06:13 UTCEG score recompute
  2. 2026-08-21 06:13 UTCGHSA enrichment
  3. 2026-08-20 22:54 UTCEPSS rescore
  4. 2026-08-20 08:28 UTCEG score recompute
  5. 2026-08-20 08:28 UTCGHSA enrichment
  6. 2026-08-19 17:02 UTCEPSS rescore
  7. 2026-08-19 10:43 UTCEG score recompute
  8. 2026-08-19 10:43 UTCGHSA enrichment
  9. 2026-08-18 13:47 UTCEPSS rescore
  10. 2026-08-18 12:51 UTCGHSA enrichment
  11. 2026-08-17 14:42 UTCEG score recompute
  12. 2026-08-17 14:42 UTCGHSA enrichment
  13. 2026-08-17 13:46 UTCEPSS rescore
  14. 2026-08-16 16:58 UTCEG score recompute
  15. 2026-08-16 16:58 UTCGHSA enrichment
  16. 2026-08-16 14:55 UTCEPSS rescore
  17. 2026-08-16 02:13 UTCEPSS rescore
  18. 2026-08-16 02:13 UTCEPSS rescore
  19. 2026-08-15 19:13 UTCEG score recompute
  20. 2026-08-15 19:13 UTCGHSA enrichment
  21. 2026-08-15 01:29 UTCEPSS rescore
  22. 2026-08-14 21:28 UTCGHSA enrichment
  23. 2026-08-13 23:43 UTCEG score recompute
  24. 2026-08-13 23:43 UTCGHSA enrichment
  25. 2026-08-13 21:59 UTCEPSS rescore
Show 34 more
  1. 2026-08-13 01:58 UTCEG score recompute
  2. 2026-08-13 01:58 UTCGHSA enrichment
  3. 2026-08-12 13:49 UTCEPSS rescore
  4. 2026-08-12 04:13 UTCEG score recompute
  5. 2026-08-12 04:13 UTCGHSA enrichment
  6. 2026-08-11 13:41 UTCEPSS rescore
  7. 2026-08-11 06:27 UTCEG score recompute
  8. 2026-08-11 06:27 UTCGHSA enrichment
  9. 2026-08-10 23:59 UTCEPSS rescore
  10. 2026-08-10 08:42 UTCEG score recompute
  11. 2026-08-10 08:42 UTCGHSA enrichment
  12. 2026-08-09 13:45 UTCEPSS rescore
  13. 2026-08-09 10:57 UTCEG score recompute
  14. 2026-08-09 10:57 UTCGHSA enrichment
  15. 2026-08-08 13:13 UTCEG score recompute
  16. 2026-08-08 13:13 UTCGHSA enrichment
  17. 2026-08-07 16:26 UTCEPSS rescore
  18. 2026-08-07 15:27 UTCEG score recompute 0.10
  19. 2026-08-07 15:27 UTCGHSA enrichment
  20. 2026-08-07 15:27 UTCNVD updateCVSS v3 → 5.9
  21. 2026-08-07 13:35 UTCGHSA enrichment
  22. 2026-08-06 15:50 UTCEG score recompute
  23. 2026-08-06 15:50 UTCGHSA enrichment
  24. 2026-08-06 13:45 UTCEPSS rescore
  25. 2026-08-06 12:33 UTCEG score recompute
  26. 2026-08-06 12:33 UTCGHSA enrichment
  27. 2026-08-05 19:16 UTCEPSS rescore
  28. 2026-08-05 14:48 UTCGHSA enrichment
  29. 2026-08-04 17:03 UTCEG score recompute
  30. 2026-08-04 17:03 UTCGHSA enrichment
  31. 2026-08-04 15:09 UTCEPSS rescore
  32. 2026-08-03 19:18 UTCEG score recompute
  33. 2026-08-03 18:23 UTCEG score recompute
  34. 2026-08-03 18:23 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2025-15630?
CVE-2025-15630 is a medium vulnerability published on August 3, 2026. A race condition exists in the cloud-based Omada device adoption process when an attacker may be able to interact with the adoption workflow before a legitimate device completes registration, resulting in provisioning information being delivered to an attacker. Successful exploitation may allow…
When was CVE-2025-15630 disclosed?
CVE-2025-15630 was first published in the National Vulnerability Database on August 3, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-15630 actively exploited?
CVE-2025-15630 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.9% of all scored CVEs.
What is the CVSS score of CVE-2025-15630?
CVE-2025-15630 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2025-15630?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-15630, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-15630

Explore →

Is Your Infrastructure Affected by CVE-2025-15630?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.