CVE-2026-79376

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-08. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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

An issue in the l2cap_handle_data() function of Bestechnic Co., Ltd BES2300 Bluetooth Audio SoC firmware v3.x and earlier allows attackers to cause a Denial of Service (DoS) via sending a crafted L2CAP packet.

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

Published

September 8, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
No patch confirmed yet.
generic
https://www.bestechnic.com/CVE-2026-79376.pdf

Vendor Advisories for CVE-2026-79376(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 45× 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 15:11 UTCGHSA enrichment
  2. 2026-09-19 03:15 UTCEG score recompute
  3. 2026-09-19 03:15 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 15:20 UTCGHSA enrichment
  6. 2026-09-18 03:25 UTCEG score recompute
  7. 2026-09-18 03:25 UTCGHSA enrichment
  8. 2026-09-17 15:30 UTCGHSA enrichment
  9. 2026-09-17 03:31 UTCGHSA enrichment
  10. 2026-09-16 15:35 UTCEG score recompute
  11. 2026-09-16 15:35 UTCGHSA enrichment
  12. 2026-09-16 14:08 UTCEPSS rescore
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-16 03:25 UTCGHSA enrichment
  15. 2026-09-15 15:29 UTCGHSA enrichment
  16. 2026-09-15 03:33 UTCEG score recompute
  17. 2026-09-15 03:33 UTCGHSA enrichment
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-14 15:38 UTCGHSA enrichment
  21. 2026-09-14 03:43 UTCEG score recompute
  22. 2026-09-14 03:43 UTCGHSA enrichment
  23. 2026-09-13 15:48 UTCGHSA enrichment
  24. 2026-09-13 03:53 UTCGHSA enrichment
  25. 2026-09-12 15:58 UTCEG score recompute
Show 20 more
  1. 2026-09-12 15:58 UTCGHSA enrichment
  2. 2026-09-12 04:03 UTCGHSA enrichment
  3. 2026-09-11 16:08 UTCEG score recompute
  4. 2026-09-11 16:08 UTCGHSA enrichment
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 04:10 UTCGHSA enrichment
  8. 2026-09-10 16:14 UTCEG score recompute
  9. 2026-09-10 16:14 UTCGHSA enrichment
  10. 2026-09-10 04:08 UTCGHSA enrichment
  11. 2026-09-09 16:08 UTCGHSA enrichment
  12. 2026-09-09 07:47 UTCEG score recompute
  13. 2026-09-09 07:47 UTCGHSA enrichment
  14. 2026-09-08 19:51 UTCGHSA enrichment
  15. 2026-09-08 18:32 UTCEG score recompute▲ 8.80
  16. 2026-09-08 18:32 UTCGHSA enrichment
  17. 2026-09-08 18:29 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  18. 2026-09-08 14:26 UTCNVD update
  19. 2026-09-08 13:50 UTCEG score recompute
  20. 2026-09-08 13:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-79376?
CVE-2026-79376 is a high vulnerability published on September 8, 2026. An issue in the l2caphandledata() function of Bestechnic Co., Ltd BES2300 Bluetooth Audio SoC firmware v3.x and earlier allows attackers to cause a Denial of Service (DoS) via sending a crafted L2CAP packet.
When was CVE-2026-79376 disclosed?
CVE-2026-79376 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-79376 actively exploited?
CVE-2026-79376 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 86.3% of all scored CVEs.
What is the CVSS score of CVE-2026-79376?
CVE-2026-79376 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-79376?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-79376, 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-79376

Explore →

Is Your Infrastructure Affected by CVE-2026-79376?

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

Start Free Scan →Browse All CVEs