CVE-2026-31773

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. 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

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: SMP: derive legacy responder STK authentication from MITM state

The legacy responder path in smp_random() currently labels the stored STK as authenticated whenever pending_sec_level is BT_SECURITY_HIGH. That reflects what the local service requested, not what the pairing flow actually achieved.

For Just Works/Confirm legacy pairing, SMP_FLAG_MITM_AUTH stays clear and the resulting STK should remain unauthenticated even if the local side requested HIGH security. Use the established MITM state when storing the responder STK so the key metadata matches the pairing result.

This also keeps the legacy path aligned with the Secure Connections code, which already treats JUST_WORKS/JUST_CFM as unauthenticated.

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
21%
KEV
Not listed

Published

May 1, 2026

Last Modified

August 5, 2026

Advisory Details (8)

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

Bluetooth: SMP: derive legacy responder STK authentication from MITM state - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: SMP: derive legacy responder STK authentication from MITM state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9a6d0db176f082685e0b6149700c0baf3ce2aa8b
generic

Bluetooth: SMP: derive legacy responder STK authentication from MITM state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9a38659a3d06080715691bd3139f9c4b61f688e3
generic

Bluetooth: SMP: derive legacy responder STK authentication from MITM state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/929db734d12db41ca5f95424db4612397f1bd4a7
generic

Bluetooth: SMP: derive legacy responder STK authentication from MITM state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/667f44f1392df6482483756458c48670e579e9ff
generic

Bluetooth: SMP: derive legacy responder STK authentication from MITM state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/20756fec2f0108cb88e815941f1ffff88dc286fe
generic

Bluetooth: SMP: derive legacy responder STK authentication from MITM state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0afc846bd80073ffcd2b8040f2b2fafaea3d9f72
generic

Bluetooth: SMP: derive legacy responder STK authentication from MITM state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/061ee71ac6b03c9f8432fe49538c3682bfcf4cf3

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
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

(24)

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 5× in last 7d / 32× 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 252 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31773?
CVE-2026-31773 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SMP: derive legacy responder STK authentication from MITM state The legacy responder path in smp_random() currently labels the stored STK as authenticated whenever pendingseclevel is BTSECURITYHIGH. That reflects what…
When was CVE-2026-31773 disclosed?
CVE-2026-31773 was first published in the National Vulnerability Database on May 1, 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-31773 actively exploited?
CVE-2026-31773 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 79.3% of all scored CVEs.
What is the CVSS score of CVE-2026-31773?
CVE-2026-31773 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-31773?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31773, 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-31773

Explore →

Is Your Infrastructure Affected by CVE-2026-31773?

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

Start Free Scan →Browse All CVEs