CVE-2026-17610

MEDIUMPre-NVD 6.06.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

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

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

In SiSDK v2026.6.0 and earlier, high network traffic loads can cause a dropped ACK leading to a denial of service. This is only present for EFR32MG24 and EFR32MG26 devices running concurrent multiprotocol Zigbee and Thread.

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

Published

August 27, 2026

Last Modified

September 8, 2026

Advisory Details (2)

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

GitHub - SiliconLabsSoftware/sisdk-release: Simplicity GA release repo · GitHub

https://github.com/SiliconLabsSoftware/sisdk-release/tree/sisdk-2026.6
generic
https://siliconlabs.lightning.force.com/sfc/servlet.shepherd/document/download/a45Vm000000F7VpIAK?operationContext=S1

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

Frequently asked(5)

What is CVE-2026-17610?
CVE-2026-17610 is a medium vulnerability published on August 27, 2026. In SiSDK v2026.6.0 and earlier, high network traffic loads can cause a dropped ACK leading to a denial of service. This is only present for EFR32MG24 and EFR32MG26 devices running concurrent multiprotocol Zigbee and Thread.
When was CVE-2026-17610 disclosed?
CVE-2026-17610 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17610 actively exploited?
CVE-2026-17610 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 94.5% of all scored CVEs.
What is the CVSS score of CVE-2026-17610?
CVE-2026-17610 has a CVSS v3 base score of 6.0 (NVD).
How do I remediate CVE-2026-17610?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17610, 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-2026-17610

Explore →

Is Your Infrastructure Affected by CVE-2026-17610?

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

Start Free Scan →Browse All CVEs