CVE-2026-43334

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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

A fix is available — apply it.

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

Bluetooth: SMP: force responder MITM requirements before building the pairing response

smp_cmd_pairing_req() currently builds the pairing response from the initiator auth_req before enforcing the local BT_SECURITY_HIGH requirement. If the initiator omits SMP_AUTH_MITM, the response can also omit it even though the local side still requires MITM.

tk_request() then sees an auth value without SMP_AUTH_MITM and may select JUST_CFM, making method selection inconsistent with the pairing policy the responder already enforces.

When the local side requires HIGH security, first verify that MITM can be achieved from the IO capabilities and then force SMP_AUTH_MITM in the response in both rsp.auth_req and auth. This keeps the responder auth bits and later method selection aligned.

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

Published

May 8, 2026

Last Modified

August 5, 2026

Advisory Details (8)

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

Bluetooth: SMP: force responder MITM requirements before building the pairing response - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: SMP: force responder MITM requirements before building the pairing response - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: SMP: force responder MITM requirements before building the pairing response - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: SMP: force responder MITM requirements before building the pairing response - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: SMP: force responder MITM requirements before building the pairing response - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91649c02c1baaa18cedf7fb425fa1f0f852c8183
generic

Bluetooth: SMP: force responder MITM requirements before building the pairing response - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ab69426e7ecbd18a222ee2ec87ca612d30197d7
generic

Bluetooth: SMP: force responder MITM requirements before building the pairing response - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/425a22c5373d4e1b46492ab869074ebeeade61f3
generic

Bluetooth: SMP: force responder MITM requirements before building the pairing response - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01bb4045d2306c266178f49ce0c3576d237a3040

Vendor Advisories for CVE-2026-43334(1)

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

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1056.57~22.04.2) @ jammy2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-23ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1059.62~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-23ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-23ubuntu
linuxKernel @ 5.10.253—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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (125 versions)6.19.12-1—

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43334?
CVE-2026-43334 is a high vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SMP: force responder MITM requirements before building the pairing response smpcmdpairing_req() currently builds the pairing response from the initiator authreq before enforcing the local BTSECURITY_HIGH requirement. If…
When was CVE-2026-43334 disclosed?
CVE-2026-43334 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43334 actively exploited?
CVE-2026-43334 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 83.3% of all scored CVEs.
What is the CVSS score of CVE-2026-43334?
CVE-2026-43334 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-43334?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43334, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43334

Explore →

Is Your Infrastructure Affected by CVE-2026-43334?

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

Start Free Scan →Browse All CVEs