CVE-2025-15627

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory 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 mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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

A cryptographic weakness exists in the Omada adoption protocol.  The protocol relies on hard-coded cryptographic keys to establish trust and protect authentication exchanges between controllers and managed devices during device adoption.

An attacker may be able to impersonate trusted controllers or managed devices and gain access to sensitive adoption-related communications.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
39
EG Risk 39/100CISA SSVC

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%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 3, 2026

Last Modified

September 29, 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-15627(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 20× in last 7d / 92× 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.

Showing the most recent 100 of 216 total refreshes for this CVE.

  1. 2026-10-04 23:45 UTCEG score recompute
  2. 2026-10-04 23:45 UTCGHSA enrichment
  3. 2026-10-04 23:21 UTCEPSS rescore
  4. 2026-10-04 06:18 UTCEG score recompute
  5. 2026-10-04 06:18 UTCGHSA enrichment
  6. 2026-10-03 14:24 UTCEPSS rescore
  7. 2026-10-03 02:13 UTCEG score recompute
  8. 2026-10-03 02:13 UTCGHSA enrichment
  9. 2026-10-02 10:18 UTCEG score recompute
  10. 2026-10-02 10:18 UTCGHSA enrichment
  11. 2026-10-01 19:48 UTCEPSS rescore
  12. 2026-10-01 13:27 UTCGHSA enrichment
  13. 2026-10-01 02:32 UTCEG score recompute
  14. 2026-10-01 02:32 UTCGHSA enrichment
  15. 2026-09-30 15:02 UTCEPSS rescore
  16. 2026-09-30 15:02 UTCEPSS rescore
  17. 2026-09-29 14:16 UTCGHSA enrichment
  18. 2026-09-29 06:38 UTCEG score recompute
  19. 2026-09-29 06:38 UTCGHSA enrichment
  20. 2026-09-28 13:50 UTCEPSS rescore
  21. 2026-09-28 05:08 UTCGHSA enrichment
  22. 2026-09-27 18:14 UTCEG score recompute
  23. 2026-09-27 18:14 UTCGHSA enrichment
  24. 2026-09-26 15:58 UTCEPSS rescore
  25. 2026-09-26 15:57 UTCEPSS rescore
Show 75 more
  1. 2026-09-25 04:46 UTCEG score recompute
  2. 2026-09-25 04:46 UTCGHSA enrichment
  3. 2026-09-24 14:02 UTCEPSS rescore
  4. 2026-09-24 08:18 UTCGHSA enrichment
  5. 2026-09-23 21:24 UTCEG score recompute
  6. 2026-09-23 21:24 UTCGHSA enrichment
  7. 2026-09-23 13:46 UTCEPSS rescore
  8. 2026-09-23 08:21 UTCGHSA enrichment
  9. 2026-09-22 21:26 UTCEG score recompute
  10. 2026-09-22 21:26 UTCGHSA enrichment
  11. 2026-09-22 14:47 UTCEPSS rescore
  12. 2026-09-22 05:03 UTCEG score recompute
  13. 2026-09-22 05:03 UTCGHSA enrichment
  14. 2026-09-20 20:55 UTCEG score recompute
  15. 2026-09-20 20:55 UTCGHSA enrichment
  16. 2026-09-20 20:14 UTCEPSS rescore
  17. 2026-09-20 00:28 UTCEG score recompute
  18. 2026-09-20 00:28 UTCGHSA enrichment
  19. 2026-09-19 13:33 UTCGHSA enrichment
  20. 2026-09-19 00:11 UTCEG score recompute
  21. 2026-09-19 00:11 UTCGHSA enrichment
  22. 2026-09-18 19:27 UTCEPSS rescore
  23. 2026-09-18 13:17 UTCGHSA enrichment
  24. 2026-09-18 01:10 UTCEG score recompute
  25. 2026-09-18 01:10 UTCGHSA enrichment
  26. 2026-09-17 01:14 UTCEG score recompute
  27. 2026-09-17 01:14 UTCGHSA enrichment
  28. 2026-09-16 14:06 UTCEPSS rescore
  29. 2026-09-16 05:18 UTCEG score recompute
  30. 2026-09-16 05:18 UTCGHSA enrichment
  31. 2026-09-16 05:13 UTCEPSS rescore
  32. 2026-09-15 16:55 UTCEG score recompute
  33. 2026-09-15 16:55 UTCGHSA enrichment
  34. 2026-09-15 03:08 UTCEPSS rescore
  35. 2026-09-15 01:50 UTCGHSA enrichment
  36. 2026-09-14 10:13 UTCGHSA enrichment
  37. 2026-09-13 22:51 UTCEG score recompute
  38. 2026-09-13 22:51 UTCGHSA enrichment
  39. 2026-09-13 16:45 UTCEPSS rescore
  40. 2026-09-13 11:57 UTCGHSA enrichment
  41. 2026-09-13 01:03 UTCEG score recompute
  42. 2026-09-13 01:03 UTCGHSA enrichment
  43. 2026-09-12 14:59 UTCEPSS rescore
  44. 2026-09-12 14:09 UTCGHSA enrichment
  45. 2026-09-12 03:14 UTCGHSA enrichment
  46. 2026-09-11 16:19 UTCEG score recompute
  47. 2026-09-11 16:19 UTCGHSA enrichment
  48. 2026-09-11 14:51 UTCEPSS rescore
  49. 2026-09-11 09:35 UTCEPSS rescore
  50. 2026-09-11 05:07 UTCGHSA enrichment
  51. 2026-09-10 18:13 UTCEG score recompute
  52. 2026-09-10 18:13 UTCGHSA enrichment
  53. 2026-09-10 09:33 UTCEPSS rescore
  54. 2026-09-10 06:49 UTCGHSA enrichment
  55. 2026-09-09 19:38 UTCGHSA enrichment
  56. 2026-09-09 06:45 UTCEG score recompute
  57. 2026-09-09 06:44 UTCGHSA enrichment
  58. 2026-09-08 21:59 UTCEPSS rescore
  59. 2026-09-07 18:49 UTCEG score recompute
  60. 2026-09-07 18:49 UTCGHSA enrichment
  61. 2026-09-07 16:00 UTCEPSS rescore
  62. 2026-09-06 16:33 UTCEG score recompute
  63. 2026-09-06 16:33 UTCGHSA enrichment
  64. 2026-09-06 13:46 UTCEPSS rescore
  65. 2026-09-06 05:34 UTCGHSA enrichment
  66. 2026-09-05 18:39 UTCEG score recompute
  67. 2026-09-05 18:38 UTCGHSA enrichment
  68. 2026-09-05 04:18 UTCEG score recompute
  69. 2026-09-05 04:18 UTCGHSA enrichment
  70. 2026-09-04 13:59 UTCEPSS rescore
  71. 2026-09-04 10:16 UTCEG score recompute
  72. 2026-09-04 10:16 UTCGHSA enrichment
  73. 2026-09-04 05:05 UTCEPSS rescore
  74. 2026-09-03 20:45 UTCGHSA enrichment
  75. 2026-09-03 08:43 UTCEG score recompute

Frequently asked(5)

What is CVE-2025-15627?
CVE-2025-15627 is a high vulnerability published on August 3, 2026. A cryptographic weakness exists in the Omada adoption protocol. The protocol relies on hard-coded cryptographic keys to establish trust and protect authentication exchanges between controllers and managed devices during device adoption. An attacker may be able to impersonate trusted controllers or…
When was CVE-2025-15627 disclosed?
CVE-2025-15627 was first published on August 3, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-15627 actively exploited?
CVE-2025-15627 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-15627?
CVE-2025-15627 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-15627?
No fix for CVE-2025-15627 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2025-15627 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-15627?

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