CVE-2025-15631

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM 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.3%CVSS: 5.9Exploit: 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 affected Omada devices where site credentials are protected using a legacy hashing algorithm that does not provide sufficient protection.

An attacker who obtains access to stored credential data may be able to recover valid credentials to gain unauthorized access to affected devices or management environments.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
31
EG Risk 31/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
Severity59% × 45%
Exploitation0% × 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.3%
EPSS %ILE
20th
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 fix on record 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-15631(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 13× in last 7d / 65× 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 165 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-15631?
CVE-2025-15631 is a medium vulnerability published on August 3, 2026. A cryptographic weakness exists in affected Omada devices where site credentials are protected using a legacy hashing algorithm that does not provide sufficient protection. An attacker who obtains access to stored credential data may be able to recover valid credentials to gain unauthorized access…
When was CVE-2025-15631 disclosed?
CVE-2025-15631 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-15631 actively exploited?
CVE-2025-15631 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-15631?
CVE-2025-15631 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2025-15631?
No fix for CVE-2025-15631 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-15631 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-15631?

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