BlueALSA (bluez-alsa/bluealsad) contains a division-by-zero vulnerability in the LC3plus sink decoder (a2dp-lc3plus.c, a2dp_lc3plus_dec_thread) that allows a Bluetooth-adjacent attacker to crash the daemon by sending a crafted RTP media header with an attacker-controlled frame count field set to zero. Attackers can establish an A2DP source connection with an LC3plus session negotiated against a victim running bluealsad as an A2DP sink and transmit a non-fragmented LC3plus media header with a zero frame count to trigger a SIGFPE in the decoding thread, causing a denial of service on builds compiled with LC3plus support enabled.
CVE-2026-101887
LOWPre-NVD 3.53.5—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 3.5 from GitHub Security Advisory (severity: LOW) published 2026-10-01. A secondary CVSS source baseline 3.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
3.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 3.5Exploit: None knownExposed services: Not assessed
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 3.5
- EG Score
- 3.5LOWhigh confidence
- EG Risk
- 16EG Risk 16/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 computedSeverity35% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix. - EPSS PROB
- 0.2%
- EPSS %ILE
- 3rd
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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
October 1, 2026
Last Modified
October 1, 2026
References (2)
Vendor Advisories for CVE-2026-101887(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| bluez-alsa | 4.0.0-2 ... 4.3.1-3.1 (8 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| bluez-alsa | 4.3.1-3, 4.3.1-3.1 |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| bluez-alsa | 4.3.1-3, 4.3.1-3.1 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× 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.
- 2026-10-04 23:21 UTCEPSS rescore
- 2026-10-04 13:41 UTCEG score recompute
- 2026-10-04 13:41 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-01 20:30 UTCEG score recompute
- 2026-10-01 20:29 UTCGHSA enrichment
- 2026-10-01 19:23 UTCEG score recompute
- 2026-10-01 19:23 UTCGHSA enrichment
- 2026-10-01 15:13 UTCGHSA enrichment
- 2026-10-01 03:35 UTCEG score recompute
- 2026-10-01 03:35 UTCGHSA enrichment
- 2026-10-01 02:46 UTCEG score recompute
- 2026-10-01 02:45 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-101887?
CVE-2026-101887 is a low vulnerability published on October 1, 2026. BlueALSA (bluez-alsa/bluealsad) contains a division-by-zero vulnerability in the LC3plus sink decoder (a2dp-lc3plus.c, a2dplc3plusdec_thread) that allows a Bluetooth-adjacent attacker to crash the daemon by sending a crafted RTP media header with an attacker-controlled frame count field set to…
When was CVE-2026-101887 disclosed?
CVE-2026-101887 was first published on October 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-101887 actively exploited?
CVE-2026-101887 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-101887?
CVE-2026-101887 has a CVSS base score of 3.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-101887?
No fix for CVE-2026-101887 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-2026-101887 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-101887
Is Your Infrastructure Affected by CVE-2026-101887?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.