CVE-2026-19774

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-15. A secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.1Exploit: None knownExposed services: Not assessed

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

BlueZ A2DP Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of BlueZ. An attacker must first obtain the ability to pair a malicious Bluetooth device with the target system in order to exploit this vulnerability.

The specific flaw exists within the handling of the stream endpoints. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-29429.

CVSS v3
7.1
EG Score
7.1HIGHhigh confidence
EG Risk
32
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
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.3%
EPSS %ILE
16th
KEV
Not listed

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

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 total (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

September 15, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
No patch confirmed yet. Sources: github_pr.
github_pr

[PW_SID:1114843] [BlueZ,v2] a2dp: Fix handling of codec capability storage

Upstream fix in progress (PR #2251 · bluez/bluez, state=closed)

https://github.com/bluez/bluez/pull/2251
generic

ZDI-26-589 - TrendAI™ Zero Day Initiative™ (ZDI)

https://www.zerodayinitiative.com/advisories/ZDI-26-589/

Vendor Advisories for CVE-2026-19774(2)

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)
PackageVulnerable rangeFix by version rangeDependents
bluez5.66-1 ... 5.87-4 (28 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
bluez5.82-1.1 ... 5.87-4 (12 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
bluez5.82-1.1 ... 5.85-4 (8 versions)
  • every version up to 5.87-1: fixed in 5.87-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-19774?
CVE-2026-19774 is a high vulnerability published on September 15, 2026. BlueZ A2DP Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of BlueZ. An attacker must first obtain the ability to pair a malicious Bluetooth device with the target system in…
When was CVE-2026-19774 disclosed?
CVE-2026-19774 was first published on September 15, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19774 actively exploited?
CVE-2026-19774 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19774?
CVE-2026-19774 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-19774?
No fix for CVE-2026-19774 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-19774 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-19774

Explore →

Is Your Infrastructure Affected by CVE-2026-19774?

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