CVE-2026-43134

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.1EG
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.1Exploit: None knownExposed: 0

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

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ

This adds a check for encryption key size upon receiving L2CAP_LE_CONN_REQ which is required by L2CAP/LE/CFC/BV-15-C which expects L2CAP_CR_LE_BAD_KEY_SIZE.

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

Published

May 6, 2026

Last Modified

May 12, 2026

Advisory Details (8)

Auto-updated May 12, 2026
No patch confirmed yet.
generic

Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fa6ad76fa8623c0a50d529cd5726fa5d819a3be4
generic

Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ec91078e132179b04e0c3906b599816c056ceaad
generic

Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96581749c7c14fbec32c35728520867929600041
generic

Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9118601ff90b79e8df3c0c98f48ae00c1b02ecef
generic

Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8dd43f9a9323f9c01bc8246da8d81a4c783c9e97
generic

Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/481ea39b342c347b6ac029f3d418486280be4e45
generic

Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/335071c0c3637064ec250481f589075db44fe4e6
generic

Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/138d7eca445ef37a0333425d269ee59900ca1104

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.252—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43134?
CVE-2026-43134 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix missing key size check for L2CAPLECONN_REQ This adds a check for encryption key size upon receiving L2CAPLECONN_REQ which is required by L2CAP/LE/CFC/BV-15-C which expects L2CAPCRLEBADKEY_SIZE.
When was CVE-2026-43134 disclosed?
CVE-2026-43134 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43134 actively exploited?
CVE-2026-43134 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 92.6% of all scored CVEs.
What is the CVSS score of CVE-2026-43134?
CVE-2026-43134 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-43134?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43134, 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-43134

Explore →

Is Your Infrastructure Affected by CVE-2026-43134?

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

Start Free Scan →Browse All CVEs