CVE-2020-10061

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.6% (46th percentile of EPSS-scored CVEs). 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, nvd
8.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.1Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

Improper handling of the full-buffer case in the Zephyr Bluetooth implementation can result in memory corruption. This issue affects: zephyrproject-rtos zephyr version 2.2.0 and later versions, and version 1.14.0 and later versions.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
41
EG Risk 41/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
Severity81% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: An upstream fix is merged but not yet in a tagged release. 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 until it ships, then apply the release.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

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

An upstream fix is merged but not yet in a tagged release. 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 until it ships, then apply the release.

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

June 5, 2020

Last Modified

November 21, 2024

Advisory Details (6)

Auto-updated Sep 16, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

Bluetooth: controller: legacy: Fix regression handling tx pool corruption

Fix merged in zephyrproject-rtos/zephyr PR #23517 on 2020-03-18 — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/pull/23517
github_pr

Bluetooth: controller: split: Fix regression handling invalid packet sequence

Fix merged in zephyrproject-rtos/zephyr PR #23516 on 2020-03-18 — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/pull/23516
github_pr

[backport v1.14] Bluetooth: controller: legacy: Backport v2.2 to v1.14-branch

Fix merged in zephyrproject-rtos/zephyr PR #23091 on 2020-11-17 — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/pull/23091
generic

Vulnerabilities — Zephyr Project Documentation

https://docs.zephyrproject.org/latest/security/vulnerabilities.html#cve-2020-10061
generic

Jira

https://zephyrprojectsec.atlassian.net/browse/ZEPSEC-75
github_pr

[backport v2.2] Bluetooth: controller: split: Fix regression in handling invalid pkt seq

Fix merged in zephyrproject-rtos/zephyr PR #23547 on 2020-04-22 — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/pull/23547

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 23× 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 157 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-10061?
CVE-2020-10061 is a high vulnerability published on June 5, 2020. Improper handling of the full-buffer case in the Zephyr Bluetooth implementation can result in memory corruption. This issue affects: zephyrproject-rtos zephyr version 2.2.0 and later versions, and version 1.14.0 and later versions.
When was CVE-2020-10061 disclosed?
CVE-2020-10061 was first published on June 5, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-10061 actively exploited?
CVE-2020-10061 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-10061?
CVE-2020-10061 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2020-10061?
An upstream fix for CVE-2020-10061 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-10061

Explore →

Is Your Infrastructure Affected by CVE-2020-10061?

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

Book a Demo →Browse All CVEs