CVE-2025-15628

HIGHNVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-03. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

Affected Omada devices rely on embedded certificates that are shared across deployments to establish trust between controllers and managed devices.

An attacker who obtains the embedded certificates may be able to impersonate trusted controllers or devices and intercept affected communications.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
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-15628(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 25× in last 7d / 70× 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-20 22:54 UTCEPSS rescore
  2. 2026-08-20 20:11 UTCGHSA enrichment
  3. 2026-08-20 08:06 UTCGHSA enrichment
  4. 2026-08-19 20:01 UTCEG score recompute
  5. 2026-08-19 20:01 UTCGHSA enrichment
  6. 2026-08-19 17:02 UTCEPSS rescore
  7. 2026-08-19 07:55 UTCGHSA enrichment
  8. 2026-08-18 19:50 UTCGHSA enrichment
  9. 2026-08-18 07:45 UTCGHSA enrichment
  10. 2026-08-17 19:36 UTCEG score recompute
  11. 2026-08-17 19:36 UTCGHSA enrichment
  12. 2026-08-17 13:46 UTCEPSS rescore
  13. 2026-08-17 05:46 UTCGHSA enrichment
  14. 2026-08-16 17:13 UTCEG score recompute
  15. 2026-08-16 17:13 UTCGHSA enrichment
  16. 2026-08-16 14:55 UTCEPSS rescore
  17. 2026-08-16 05:08 UTCEG score recompute
  18. 2026-08-16 05:08 UTCGHSA enrichment
  19. 2026-08-16 02:13 UTCEPSS rescore
  20. 2026-08-16 02:13 UTCEPSS rescore
  21. 2026-08-15 17:03 UTCGHSA enrichment
  22. 2026-08-15 04:58 UTCEG score recompute
  23. 2026-08-15 04:58 UTCGHSA enrichment
  24. 2026-08-15 01:29 UTCEPSS rescore
  25. 2026-08-14 16:52 UTCGHSA enrichment
Show 45 more
  1. 2026-08-14 04:46 UTCEG score recompute
  2. 2026-08-14 04:46 UTCGHSA enrichment
  3. 2026-08-13 21:59 UTCEPSS rescore
  4. 2026-08-13 16:41 UTCGHSA enrichment
  5. 2026-08-13 04:24 UTCGHSA enrichment
  6. 2026-08-12 16:19 UTCEG score recompute
  7. 2026-08-12 16:19 UTCGHSA enrichment
  8. 2026-08-12 13:49 UTCEPSS rescore
  9. 2026-08-12 04:14 UTCGHSA enrichment
  10. 2026-08-11 16:08 UTCEG score recompute
  11. 2026-08-11 16:08 UTCGHSA enrichment
  12. 2026-08-11 13:41 UTCEPSS rescore
  13. 2026-08-11 04:03 UTCEG score recompute
  14. 2026-08-11 04:03 UTCGHSA enrichment
  15. 2026-08-10 23:59 UTCEPSS rescore
  16. 2026-08-10 15:58 UTCGHSA enrichment
  17. 2026-08-10 03:53 UTCGHSA enrichment
  18. 2026-08-09 15:48 UTCEG score recompute
  19. 2026-08-09 15:48 UTCGHSA enrichment
  20. 2026-08-09 13:45 UTCEPSS rescore
  21. 2026-08-09 03:43 UTCEG score recompute
  22. 2026-08-09 03:43 UTCGHSA enrichment
  23. 2026-08-08 15:38 UTCGHSA enrichment
  24. 2026-08-08 03:33 UTCEG score recompute
  25. 2026-08-08 03:33 UTCGHSA enrichment
  26. 2026-08-07 16:26 UTCEPSS rescore
  27. 2026-08-07 15:27 UTCEG score recompute 0.70
  28. 2026-08-07 15:27 UTCGHSA enrichment
  29. 2026-08-07 15:27 UTCNVD updateCVSS v3 → 7.5
  30. 2026-08-07 03:55 UTCGHSA enrichment
  31. 2026-08-06 15:50 UTCEG score recompute
  32. 2026-08-06 15:50 UTCGHSA enrichment
  33. 2026-08-06 13:45 UTCEPSS rescore
  34. 2026-08-06 07:47 UTCGHSA enrichment
  35. 2026-08-05 19:42 UTCEG score recompute
  36. 2026-08-05 19:42 UTCGHSA enrichment
  37. 2026-08-05 19:16 UTCEPSS rescore
  38. 2026-08-05 07:37 UTCGHSA enrichment
  39. 2026-08-04 19:31 UTCEG score recompute
  40. 2026-08-04 19:31 UTCGHSA enrichment
  41. 2026-08-04 15:09 UTCEPSS rescore
  42. 2026-08-04 07:25 UTCGHSA enrichment
  43. 2026-08-03 19:18 UTCEG score recompute
  44. 2026-08-03 18:23 UTCEG score recompute
  45. 2026-08-03 18:23 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2025-15628?
CVE-2025-15628 is a high vulnerability published on August 3, 2026. Affected Omada devices rely on embedded certificates that are shared across deployments to establish trust between controllers and managed devices. An attacker who obtains the embedded certificates may be able to impersonate trusted controllers or devices and intercept affected communications.
When was CVE-2025-15628 disclosed?
CVE-2025-15628 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-15628 actively exploited?
CVE-2025-15628 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 86.9% of all scored CVEs.
What is the CVSS score of CVE-2025-15628?
CVE-2025-15628 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-15628?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-15628, 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-15628

Explore →

Is Your Infrastructure Affected by CVE-2025-15628?

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