CVE-2025-7375

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

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

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

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

A denial-of-service (DoS) vulnerability was identified in Omada EAP610 v3. An attacker with adjacent network access can send crafted requests to cause the device’s HTTP service to crash. This results in temporary service unavailability until the device is rebooted. This issue affects Omada EAP610 firmware versions prior to 1.6.0.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

March 5, 2026

Last Modified

June 17, 2026

Advisory Details (3)

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

EAP610 | AX1800 Ceiling Mount WiFi 6 Access Point | Omada Network Support

https://support.omadanetworks.com/us/product/eap610/v3/
generic

Security Advisory on Unauthenticated Denial-of-Service Vulnerability on Omada EAP610 (CVE-2025-7375) | Omada Network Support

https://support.omadanetworks.com/us/document/118100/
generic
https://support.omadanetworks.com/en/product/eap610/v3/

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 24× 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-09-18 19:27 UTCEPSS rescore
  2. 2026-09-17 19:30 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:14 UTCEPSS rescore
  5. 2026-09-15 03:10 UTCEPSS rescore
  6. 2026-09-13 16:46 UTCEPSS rescore
  7. 2026-09-12 15:00 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-11 09:36 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:00 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:11 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-08-30 01:21 UTCEPSS rescore
  18. 2026-08-28 21:40 UTCEPSS rescore
  19. 2026-08-27 14:24 UTCEPSS rescore
  20. 2026-08-26 14:45 UTCEPSS rescore
  21. 2026-08-25 13:48 UTCEPSS rescore
  22. 2026-08-24 14:16 UTCEPSS rescore
  23. 2026-08-23 00:18 UTCEPSS rescore
  24. 2026-08-21 23:48 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 42 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:46 UTCEPSS rescore
  3. 2026-08-16 14:55 UTCEPSS rescore
  4. 2026-08-16 12:25 UTCEG score recompute
  5. 2026-08-16 12:25 UTCGHSA enrichment
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-14 08:23 UTCEG score recompute
  9. 2026-08-14 08:23 UTCGHSA enrichment
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-12 23:58 UTCEG score recompute
  12. 2026-08-12 23:58 UTCGHSA enrichment
  13. 2026-08-12 13:50 UTCEPSS rescore
  14. 2026-08-11 13:42 UTCEPSS rescore
  15. 2026-08-11 05:29 UTCEG score recompute
  16. 2026-08-11 05:29 UTCGHSA enrichment
  17. 2026-08-10 23:59 UTCEPSS rescore
  18. 2026-08-10 07:28 UTCEG score recompute
  19. 2026-08-10 07:28 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 08:01 UTCEG score recompute
  22. 2026-08-09 08:01 UTCGHSA enrichment
  23. 2026-08-08 16:36 UTCEPSS rescore
  24. 2026-08-07 19:40 UTCEG score recompute
  25. 2026-08-07 19:40 UTCGHSA enrichment
  26. 2026-08-07 16:27 UTCEPSS rescore
  27. 2026-08-06 13:46 UTCEPSS rescore
  28. 2026-08-06 02:30 UTCEG score recompute
  29. 2026-08-06 02:30 UTCGHSA enrichment
  30. 2026-08-05 19:17 UTCEPSS rescore
  31. 2026-08-04 02:02 UTCEG score recompute
  32. 2026-08-04 02:02 UTCGHSA enrichment
  33. 2026-08-03 10:35 UTCEPSS rescore
  34. 2026-08-02 18:43 UTCEG score recompute
  35. 2026-08-02 18:43 UTCGHSA enrichment
  36. 2026-08-02 02:26 UTCEPSS rescore
  37. 2026-08-01 04:15 UTCEPSS rescore
  38. 2026-07-30 16:27 UTCEPSS rescore
  39. 2026-07-30 01:30 UTCEPSS rescore
  40. 2026-07-27 14:13 UTCEPSS rescore
  41. 2026-07-27 13:51 UTCEG score recompute
  42. 2026-07-27 13:51 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-7375?
CVE-2025-7375 is a medium vulnerability published on March 5, 2026. A denial-of-service (DoS) vulnerability was identified in Omada EAP610 v3. An attacker with adjacent network access can send crafted requests to cause the device’s HTTP service to crash. This results in temporary service unavailability until the device is rebooted. This issue affects Omada EAP610…
When was CVE-2025-7375 disclosed?
CVE-2025-7375 was first published in the National Vulnerability Database on March 5, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-7375 actively exploited?
CVE-2025-7375 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 87.4% of all scored CVEs.
What is the CVSS score of CVE-2025-7375?
CVE-2025-7375 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2025-7375?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-7375, 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-7375

Explore →

Is Your Infrastructure Affected by CVE-2025-7375?

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

Start Free Scan →Browse All CVEs